DO NOT REPLY [Bug 30373] New: - Image Task flattens all directory structures.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30373] - Image Task flattens all directory structures.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30374] New: - There is no way to compare a the value of a variable specified in a properties file inside the ant build script.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: JIRA migration

Stefan Bodewig wrote: On Tue, 27 Jul 2004, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: I wonder whether we should start a new vote on this issue, or is there a compelling reason to stay with Bugzilla ? Is there a compelling reason to move? There is no compelling reason to move. JIRA

Re: JIRA migration

Stefan Bodewig wrote: On Tue, 27 Jul 2004, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: I wonder whether we should start a new vote on this issue, or is there a compelling reason to stay with Bugzilla ? Is there a compelling reason to move? The best reason to move would be the relative lack of

DO NOT REPLY [Bug 30374] - There is no way to compare a the value of a variable specified in a properties file inside the ant build script.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[GUMP@brutus]: ant/test-ant success

/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons/net/dist/commons-net-20040729.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar:/usr/local/gump/public

Re: cvs commit: ant/src/main/org/apache/tools/ant/taskdefs/optional/dotnet WsdlToDotnet.java

Stefan Bodewig wrote: On Wed, 28 Jul 2004, Steve Loughran <[EMAIL PROTECTED]> wrote: Does mono handle a list of schemas/urls to schemas after the first file? $ man wsdl wsdl(1) wsdl(1) NAME wsdl - Mono's Web Service Proxy Generator SYNOPSIS

Re: mutex tasks

[EMAIL PROTECTED] wrote: I'm just curious about how usefull other folks would find this. I've created 2 tasks and . The use case is where you have parallel ants running (on some server) doing builds, but 1 part of the build (in our case, some JFCUnit) needs to be single threaded. By this I mean th

DO NOT REPLY [Bug 30380] New: - shutdown hook for xmllogger

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: mutex tasks

I've just dome some testing in XP. The locks are simply zero length files and nothing more. Also, because of the random backoff approach, I think it would be pretty robust. To clean up any locks left over from previous attempts, a mastster scheduler could simply remove all files in the locks direct

Re: mutex tasks

David, You're far better (from the atomicity and portability points-of-view) creating a directory instead of a file - directories can't be re-created on any filesystem I've used while files can be (so you might think you created the lock file but didn't due to a race condition). Phil :n. On Thu,

Re: mutex tasks

I removed the race condition by having each parallel ant process using a unique name. That is really up to the build file, but that is the way it was designed. So, there shouldn't be any race condition. If 2 files get created at the same time, each task will remove their own file and do a random b

Xalan1/2.jar

ant-xalan2.jar has disappeared in Ant 1.6.2, and the Xalan2Executor in now in ant-junit.jar, and Xalan1Executor is in both ant-junit.jar and ant-xalan1.jar. Is this normal? I probably missed the posts on this issue. Does anyone remember? Thanks, --DD ---

Re: Xalan1/2.jar

ant-xalan2 has been removed intentionally. [1] Whether it is good that Xalan1Executor is in two jars is another issue. Antoine [1] http://marc.theaimsgroup.com/?l=ant-dev&m=108617827426803&w=2 Dominique Devienne wrote: ant-xalan2.jar has disappeared in Ant 1.6.2, and the Xalan2Executor in now in an

DO NOT REPLY [Bug 30397] New: - execute special target before ant exits on failure of any target

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30397] - execute special target before ant exits on failure of any target

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu