DO NOT REPLY [Bug 21421] - [Patch] to allow to run several targets without rerunning their dependencies

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21421] - [Patch] to allow to run several targets without rerunning their dependencies

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21192] - documentation hard to read because of incorrect block-quoting style

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://nagoya.apache.org/bugzilla/show_bu

RE: [Patch] Re: StarTeam checkout task behavior changes between 1.5.1 and 1.5.3

Please submit this as a bug report to Bugzilla. The place your patch is changing is used in many situations other than the one you are interested in and would almost certainly have negative consequences in some other context. What you are trying to fix needs to be fixed in a different way. -

[Patch] Re: StarTeam checkout task behavior changes between 1.5.1 and 1.5.3

Weiqi Gao wrote: Hi, I have observed some behavioral changed of the StarTeam checkout task stcheckout between Ant 1.5.1 and Ant 1.5.3. I'm using the task this way: I switched from using Ant 1.5.1 to Ant 1.5.3 last week, and experienced two changes of behavior: 1. An empty set of work

DO NOT REPLY [Bug 21421] - [Patch] to allow to run several targets without rerunning their dependencies

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21421] - [Patch] to allow to run several targets without rerunning their dependencies

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21421] New: - [Patch] to allow to run several targets without rerunning their dependencies

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://nagoya.apache.org/bugzilla/show_bu

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 02:47:00PM -0400, Victor J. Orlikowski wrote: > On Tue, Jul 08, 2003 at 02:29:36PM -0400, Victor J. Orlikowski wrote: > > Ugh, quite right. Neither had the two-arg version. My mistake. > > > > OK, I'm perfectly amenable to putting back the 5-arg versions, and > > marking th

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 02:29:36PM -0400, Victor J. Orlikowski wrote: > Ugh, quite right. Neither had the two-arg version. My mistake. > > OK, I'm perfectly amenable to putting back the 5-arg versions, and > marking them as deprecated; your patch covers that, Stefan, though > I may make minor chan

DO NOT REPLY [Bug 21414] - Bugzilla Report Generator Task

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://nagoya.apache.org/bugzilla/show_bu

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 04:57:34PM +0200, Stefan Bodewig wrote: > On Tue, 8 Jul 2003, Victor J. Orlikowski > <[EMAIL PROTECTED]> wrote: > > > Hence, the BSFManager exec() method should now take the language > > and script parameters only, as was the case in 2.2. > > Neither 2.2 nor 2.3.0-rc have

DO NOT REPLY [Bug 21414] New: - Bugzilla Report Generator Task

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://nagoya.apache.org/bugzilla/show_bu

AW: [Patch] keep-alive feature

> I've learned that anything slated for Ant 2.0 is doomed with > failure... Ok, let´s start "Ant 2003" or "Ant XP" :-) Jan

RE: [Patch] keep-alive feature

I've learned that anything slated for Ant 2.0 is doomed with failure... And since ant:type is going in with 1.6, so should ant:if and co., IMHO that is ;-) --DD > -Original Message- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 11:15 AM > To: Ant Develope

Re: [Patch] keep-alive feature

Dominique Devienne wrote: This discussing brings back the still pending issue of having a generic if/unless on all tasks/types to name just an example... failonerror, if/unless, ant:type, and some other attributes most likely, control 'aspects' of the build, that should be dealt with in a single pl

DO NOT REPLY [Bug 21387] - [PATCH] Permit to turn on Java (1.4) assertions in tests + tested code

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://nagoya.apache.org/bugzilla/show_bu

RE: [Patch] keep-going feature

Opps, sorry that should be keep-going (anyway). Yep, you are right the build does fail, so it is not equivalent to an implicit fail-on-error attribute on each target (which I think would be extremely confusing). Peter. ps: perhaps we could put the link in the main ant page just after the "mak

RE: [Patch] keep-alive feature

Actually the reason to implement keep-alive (originally keep-going) is to find as many problems as possible. It is done by executing all targets that do not depend directly or indirectly on failed targets. It is not fail-on-error flag - the build will still fail. There is a link that explaining th

DO NOT REPLY [Bug 21320] - Copy task ignores all but first file returned by FileNameMapper

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21320] - Copy task ignores all but first file returned by FileNameMapper

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 13323] - Property files loose formating when use propertyfile task

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 18667] - javah module no longer works with Java 1.4.2

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21410] - javah task doesn't work w/ j2sdk1.4.2

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://nagoya.apache.org/bugzilla/show_bu

Re: [Patch] keep-alive feature

On Tue, 2003-07-08 at 16:06, Stefan Bodewig wrote: > On 08 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > > The keep-alive feature is not quite the same > > as a fail-on-error on each task, it is more > > like a fail-on-error for each target. > > So be it, add it to Target as well 8-) > >

DO NOT REPLY [Bug 21410] New: - javah task doesn't work w/ j2sdk1.4.2

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://nagoya.apache.org/bugzilla/show_bu

RE: [Patch] keep-alive feature

Are you saying I'm repeating myself ;-) I sure am, am I? Pluggeable aspects came to me too, I just didn't think throwing it out as well would have helped much the chances of aspects getting to 1.6... Short of using real AOP like AspectJ, I don't see how Pluggeable aspects can be implemented than

Re: New Laucher

On Tue, 8 Jul 2003, Conor MacNeill <[EMAIL PROTECTED]> wrote: > It turns out this "legacy" code works better than the commented out > code because it handles spaces in file names (which are otherwise > rendered as %20) Yes, the URI handling code in FileUtils is better than the code in the JDK, at

Re: [Patch] keep-alive feature

On 08 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > The keep-alive feature is not quite the same > as a fail-on-error on each task, it is more > like a fail-on-error for each target. So be it, add it to Target as well 8-) What would you want to see happen with keep-alive enabled and failon

Re: [Patch] keep-alive feature

On Tue, 8 Jul 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > failonerror, if/unless, ant:type, and some other attributes most > likely, control 'aspects' of the build, that should be dealt with in > a single place! Well, it's not exactly as if we were having that discussion for the first t

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, 8 Jul 2003, Victor J. Orlikowski <[EMAIL PROTECTED]> wrote: > Hence, the BSFManager exec() method should now take the language > and script parameters only, as was the case in 2.2. Neither 2.2 nor 2.3.0-rc have a two-arg version of BSFManager#exec. If I change Ant to pass only two argumen

RE: Checkstyle Audit

Can't check.xml it from the Maven repository ;-) --DD > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 2:02 AM > To: [EMAIL PROTECTED] > Subject: AW: Checkstyle Audit > > And you need the checkstyle library. > http://checkstyle.sourc

RE: [Patch] keep-alive feature

This discussing brings back the still pending issue of having a generic if/unless on all tasks/types to name just an example... failonerror, if/unless, ant:type, and some other attributes most likely, control 'aspects' of the build, that should be dealt with in a single place! Now that Ant is nam

Re: [FWD] [GUMP] Build Failure - dist-ant

> > build: > > [javac] Compiling 56 source files to > > /home/rubys/jakarta/ant/build/classes > > [javac] > > /home/rubys/jakarta/ant/src/main/org/apache/tools/ant/taskdefs/optional/Script.java:122: > > exec(java.lang.String,java.lang.Object) in org.apache.bsf.BSFManager > > cannot be a

Re: New Laucher

On Thu, 3 Jul 2003 11:16 pm, Stefan Bodewig wrote: > > It's JDK 1.1 legacy as far as I'm concerned and could those be swapped > against the commented Axis' code. > It turns out this "legacy" code works better than the commented out code because it handles spaces in file names (which are otherwise

Re: [Patch] keep-alive feature

The keep-alive feature is not quite the same as a fail-on-error on each task, it is more like a fail-on-error for each target. I have test-driven it in my build env where I have a large number of c++ programs to compile. It is nice to able to change a header file and then compile all the programs

Re: Test Failures

On Tue, 2003-07-08 at 13:19, Stefan Bodewig wrote: > On 08 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > On Mon, 2003-07-07 at 09:37, Stefan Bodewig wrote: > > >> So if we agreed that it is OK to add/remove tasks to the target > >> currently being executed, we simply needed to provide a be

DO NOT REPLY [Bug 21192] - documentation hard to read because of incorrect block-quoting style

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://nagoya.apache.org/bugzilla/show_bu

[FWD] [GUMP] Build Failure - dist-ant

Dear BSF developers, hi Victor 8-) what is the recommended upgrade route for this method? > build: > [javac] Compiling 56 source files to /home/rubys/jakarta/ant/build/classes > [javac] > /home/rubys/jakarta/ant/src/main/org/apache/tools/ant/taskdefs/optional/Script.java:122: > exec(jav

Re: Test Failures

On 08 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > On Mon, 2003-07-07 at 09:37, Stefan Bodewig wrote: >> So if we agreed that it is OK to add/remove tasks to the target >> currently being executed, we simply needed to provide a better >> implemenntation than the old one. 8-) > It would be

[GUMP] Build Failure - ant-testutil

This email is autogenerated from the output from: Buildfile: build.xml prepare: check_for_optional_packages: build: [jav

[GUMP] Build Failure - dist-ant

This email is autogenerated from the output from: Buildfile: build.xml main_distribution: [mkdir] Created dir: /home/rubys/jak

Re: Test Failures

On Tue, 8 Jul 2003 06:00 pm, peter reilly wrote: > > It would be difficult to provide a different implementation. > Wouldn't cloning the list before iteration do that. It would make the changes ineffective but not terminal. Not sure if it worth the effort to prevent this scenario. > A thing to

Re: Test Failures

On Mon, 2003-07-07 at 09:37, Stefan Bodewig wrote: > On 07 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > > I am not sure that that depending on an undocumented (I think) > > feature of Vector/Enumeration is a good idea. > > I agree, though it is sort-of documented in Vector's javadocs (th

Re: [Patch] keep-alive feature

On 07 Jul 2003, peter reilly <[EMAIL PROTECTED]> wrote: > I am thinking of committing the keep-alive > feature: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=21144 > > Do any of the ant commiters have a problem with > this feature? Well, we've already introduced one magic attribute with

DO NOT REPLY [Bug 21320] - Copy task ignores all but first file returned by FileNameMapper

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21320] - Copy task ignores all but first file returned by FileNameMapper

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://nagoya.apache.org/bugzilla/show_bu

AW: AW: [Fwd: XSLT task question]

Sure: * application XML ---> common XML ---> target format * XMI --> FO --> PDF The second XSL script needs a special XML format as input. E.g. the PDF-Renderer needs FO. A HTML-Renderer needs special XML (maybe XHTML, maybe DocBook, maybe XDoc). And the first XSL script has to generate exactly

AW: Checkstyle Audit

> On Fri, 4 Jul 2003 08:10 pm, Antoine Levy-Lambert wrote: > > Hi Conor, > > I am a beotian with xml/xsl. > > How do you run the style sheets yourself against the source > code of ant ? > > Antoine > > Had to look that one up. The check.xml file contains all the > tasks necessary > to run the a

Re: Using Ant API to create build scripts

On Tue, 8 Jul 2003 11:56 am, Mirko Raner wrote: > (a) Is there something I am missing in the Ant API that would allow me > to create a build.xml file from an initialized Project object? Sort of. You need to checkout the RuntimeConfigurable. It is a DOM of sorts that is maintained by Ant. You shou

DO NOT REPLY [Bug 21387] - [PATCH] Permit to turn on Java (1.4) assertions in tests + tested code

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://nagoya.apache.org/bugzilla/show_bu

Using Ant API to create build scripts

Hi all, I am currently working on an IDE plug-in that also requires automatic generation of Ant build scripts. I had a look at the Ant API and noticed that there are classes for Projects, Targets, Tasks, etc. which are essentially created and populated by the ProjectHelper/ProjectHelper2 classes

DO NOT REPLY [Bug 21387] - [PATCH] Permit to turn on Java (1.4) assertions in tests + tested code

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21386] - Project.fireMessageLoggedEvent susceptable to incorrect state

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://nagoya.apache.org/bugzilla/show_bu

cvs commit: ant/src/main/org/apache/tools/ant Project.java

conor 2003/07/07 17:26:38 Modified:src/main/org/apache/tools/ant Project.java Log: Ensure logging message flag is reset Reported By Darin Swanson PR: 21386 Revision ChangesPath 1.144 +10 -7 ant/src/main/org/apache/tools/ant/Project.java Index: Project