Re: Property resolution in a task

[EMAIL PROTECTED] wrote: Ok, that comes from a guy who works more on DOM-Nodes than me (=nothing) :-) Should we add that to Project class? (If we are allowed to do that) sure -as long as we also have a test for it :) - To unsubscri

DO NOT REPLY [Bug 24761] - specify a target to be executed if error occurs

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: [VOTE] macrodef - do attributes as properties or substitution s

I know that Canoo WebTest uses %{x} as its own variable substitution. > -Original Message- > From: Steve Cohen [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2003 12:50 PM > To: Ant Developers List > Subject: RE: [VOTE] macrodef - do attributes as properties or > substitutions > >

DO NOT REPLY [Bug 24761] New: - specify a target to be executed if error occurs

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: Ant 1.6 and namespace

Dominique Devienne wrote: From: Christopher Lenz [mailto:[EMAIL PROTECTED] Dominique Devienne wrote: From: peter reilly [mailto:[EMAIL PROTECTED] On Monday 17 November 2003 17:01, Dominique Devienne wrote: So the NS for and does not matter? Conceptually they are part of the Ant XML dialect to me,

RE: [VOTE] macrodef - do attributes as properties or substitution s

> From: peter reilly [mailto:[EMAIL PROTECTED] > > If macrodef attribute are to be implements as substitutions, what > should be the notation? (where x is the attribute name) > > [ ] as ${x} (look like ant properties) > [ ] as $(x) > [ ] as @x > [ ] as ${attribute:x} > [ ] as @{x} > [X] some

RE: [VOTE] macrodef - do attributes as properties or substitutions

Another non committer here. I don't like $(x) because it looks too much like ${x}, although I suppose I could get used to that. Therfore, I am drawn to @{x}. ${attribute:x} is possible but way too much typing for my taste. Abbreviated to ${att:x} or ${attrib:x} my negativity level goes down accor

RE: [VOTE] macrodef - do attributes as properties or substitutions

Yes I am not a committer, but anyway ;-) [X] as $(x) +1 [X] as ${attribute:x} +0.5 Cannot decide between the two. But by using '$' I think we can resolve any issues with escaping using the rules we already have for properties. The others would require a different convention. Jose Alberto >

Re: [VOTE] macrodef - do attributes as properties or substitutions

OK, how do we want to implement attributes: current [ ] as textual substitution~ 4 [ ] as "real" Ant properties ~ 2 undecided ~ 1 If macrodef attribute are to be implements as substitutions, what should be the notation? (where x is

Re: macrodef - do attributes as properties or substitutions

On Monday 17 November 2003 15:57, Stefan Bodewig wrote: > On Fri, 14 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > > An example: > > > > > > > > > > > > > > > > > > > > > > > > inmacro is '${inmacro}' > > > > > > > > This shows: > >

RE: Ant 1.6 and namespace

> From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Dominique Devienne wrote: > >>From: peter reilly [mailto:[EMAIL PROTECTED] > >> > >>>On Monday 17 November 2003 17:01, Dominique Devienne wrote: > >>> > >>>So the NS for and does not matter? > >>>Conceptually they are part of the Ant XML dialec

Re: Ant 1.6 and namespace

Dominique Devienne wrote: From: peter reilly [mailto:[EMAIL PROTECTED] On Monday 17 November 2003 17:01, Dominique Devienne wrote: So the NS for and does not matter? Conceptually they are part of the Ant XML dialect to me, so seeing them in no namespace at all seems weird??? --DD If no namespace

Re: Ant 1.6 and namespace

On Monday 17 November 2003 17:20, Dominique Devienne wrote: > > From: peter reilly [mailto:[EMAIL PROTECTED] > > > > > On Monday 17 November 2003 17:01, Dominique Devienne wrote: > > > > > > So the NS for and does not matter? > > > Conceptually they are part of the Ant XML dialect to me, > > > so

RE: Ant 1.6 and namespace

> From: peter reilly [mailto:[EMAIL PROTECTED] > > On Monday 17 November 2003 17:01, Dominique Devienne wrote: > > > > So the NS for and does not matter? > > Conceptually they are part of the Ant XML dialect to me, > > so seeing them in no namespace at all seems weird??? --DD > > If no namespace

Re: Ant 1.6 and namespace

On Monday 17 November 2003 17:01, Dominique Devienne wrote: > > From: peter reilly [mailto:[EMAIL PROTECTED] > > > > Yes, this is std xml (not visible from ant processing code): > > > > > xmlns:ant="antlib:org.apache.tools.ant" > > xmlns:acme="antlib:org.acme.anttasks"> > > >

RE: Ant 1.6 and namespace

> From: peter reilly [mailto:[EMAIL PROTECTED] > > Yes, this is std xml (not visible from ant processing code): > > xmlns:ant="antlib:org.apache.tools.ant" > xmlns:acme="antlib:org.acme.anttasks"> > > > > > > > >

Re: Ant 1.6 and namespace

Thanks to Peter and Chris. Option B looks good to me as well... this can also be called beta1 behavior, which is less error-prone/confusing with macrodef elements, for one thing. Incidentally I'd probably use the first example more often than not. -Matt --- Christopher Lenz <[EMAIL PROTECTED]>

DO NOT REPLY [Bug 24756] New: - support property values containing refs to undefined properties

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: Ant 1.6 and namespace

Matt Benson wrote: --- peter reilly <[EMAIL PROTECTED]> wrote: For example: The arguments are equal Okay, how about redoing the same example with: ... or will that syntax be available at all? That should be:

Re: Ant 1.6 and namespace

On Monday 17 November 2003 16:11, Matt Benson wrote: > --- peter reilly <[EMAIL PROTECTED]> wrote: > > For example: > > > > > xmlns:acme="antlib:org.acme.anttasks"> > > > > > > > > > > > > > > > >The arguments are equal

RE: problems with tag - ant-1.6beta2

Here´s my build file, i think that its ok. And if I did wrong, output should give a error message not a stacktrace.

AW: problems with tag - ant-1.6beta2

Hi Edson, this stack trace shows an error occuring in a package which is not part of ant, rather of tomcat. Can you also show your build file ? Can it be that one of the parameters which you are giving in the task is wrong ? Or maybe there is a distinct task (not sure). Antoine -Ursprünglic

Re: Ant 1.6 and namespace

--- peter reilly <[EMAIL PROTECTED]> wrote: > > For example: > > xmlns:acme="antlib:org.acme.anttasks"> > > > > > > > >The arguments are equal > > > > > Okay, how about redoing the same example w

Re: Ant 1.6 and namespace

On Mon, 17 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > From the feedback, I think that we should implement option b), +1 Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

Re: macrodef - do attributes as properties or substitutions

On Fri, 14 Nov 2003, Jan Materne <[EMAIL PROTECTED]> wrote: > > > > > I don't think we should need any special cludges just to support this usecase. 8-) Give two a completely bogus, impossible to be used in any real world usage value and check for that. Should be easier than compar

Re: [VOTE] macrodef - do attributes as properties or substitutions

> OK, how do we want to implement attributes: > > [X] as textual substitution > [ ] as "real" Ant properties Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: macrodef - do attributes as properties or substitutions

On Fri, 14 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > On Friday 14 November 2003 14:07, Stefan Bodewig wrote: >> On Fri, 14 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: >> > I do not like using a different notation for attributes. >> >> unless they are a different thing than properti

Re: [PATCH] redundant quotes in runant.py

On Mon, 17 Nov 2003, Knut Wannheden <[EMAIL PROTECTED]> wrote: > the Python script passes "" as the target argument to Java. This is > turn seems to cause Ant to run the top-level tasks and return with > "BUILD SUCCESSFUL". Is this indeed the intended behaviour? Uhm, in a way, yes. The top-lev

cvs commit: ant/src/script runant.py

bodewig 2003/11/17 07:51:38 Modified:src/script Tag: ANT_16_BRANCH runant.py Log: Merge from HEAD Revision ChangesPath No revision No revision 1.4.2.2 +2 -2 ant/src/script/runant.py Index: runant.py ===

cvs commit: ant/src/script runant.py

bodewig 2003/11/17 07:49:27 Modified:src/script runant.py Log: Remove badly placed quotes, Submitted by Knut Wannheden Revision ChangesPath 1.6 +2 -2 ant/src/script/runant.py Index: runant.py ==

Ant 1.6 and namespace

Last week, I sent a questionary about namespace support in ant 1.6. http://marc.theaimsgroup.com/?l=ant-dev&m=106848848930806&w=2 >From the feedback, I think that we should implement option b), nested elements of tasks/types have the same namespace uri as the containing task/type, unless they are

problems with tag - ant-1.6beta2

Hello folks, i having some problems with jspc tag. I trying to solve or to known with is wrong here, but in my terminal i got this exception: [jspc] Compiling 3 source filesD:\tmp\classes-jsp\org\apache\jsp [jasperc] java.lang.ArrayIndexOutOfBoundsException: 9 [jasperc] at org

Re: Property resolution in a task

[EMAIL PROTECTED] wrote: Ok, that comes from a guy who works more on DOM-Nodes than me (=nothing) :-) Should we add that to Project class? (If we are allowed to do that) Christoper's code required a little work, but here's a method that works, should you choose to add it to the Project class. I n

DO NOT REPLY [Bug 23913] - Style task does not use XMLCatalog as required

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: Property resolution in a task

Ok, that comes from a guy who works more on DOM-Nodes than me (=nothing) :-) Should we add that to Project class? (If we are allowed to do that) Jan > -Original Message- > From: Upayavira [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2003 1:02 PM > To: Ant Developers List > Su

DO NOT REPLY [Bug 24712] - macrodef sequential should be implicit

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: Property resolution in a task

Christopher Lenz wrote: It should be much more efficient (and probably simpler) to just traverse the DOM and replace properties in-place: Splendid! This job gets easier by the moment! Thanks for that. Regards, Upayavira public void replaceProperties(Node n) throws DOMException { switch (n.ge

Re: Property resolution in a task

It should be much more efficient (and probably simpler) to just traverse the DOM and replace properties in-place: public void replaceProperties(Node n) throws DOMException { switch (n.getNodeType()) { case Node.ATTR_NODE: case Node.CDATA_SECTION_NODE: case Node.TEXT_NODE:

RE: Property resolution in a task

Have a look at org.apache.tools.ant.util.DOMElementWriter. Sounds that it could help you. Jan > -Original Message- > From: Upayavira [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2003 12:29 PM > To: Ant Developers List > Subject: Re: Property resolution in a task > > > [EMAIL

Re: Property resolution in a task

[EMAIL PROTECTED] wrote: Is there an Ant way to 'spider' a DOM node, replacing properties as it goes? I don´t know such a thing. But you can do: - write the DOM to a String - use Project.replace() on that String - parse the String - replace the DOM with new one Jan Yup, that should work! T

RE: Property resolution in a task

> Is there an Ant way to 'spider' a DOM node, replacing > properties as it goes? I don´t know such a thing. But you can do: - write the DOM to a String - use Project.replace() on that String - parse the String - replace the DOM with new one Jan

Re: Property resolution in a task

[EMAIL PROTECTED] wrote: String org.apache.tools.ant.Project.replaceProperties(String value) would help here. Absolutely splendid. I thought it might be that simple. One further question - I've looked deeper into the Cocoon code, and can see that we have a DOM node for which I want to replace p

DO NOT REPLY [Bug 24743] - javadoc task fails for multiple source locations

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: Property resolution in a task

String org.apache.tools.ant.Project.replaceProperties(String value) would help here. /** * Replaces ${} style constructions in the given value with the * string value of the corresponding data types. * * @param value The string to be scanned for property references.

Property resolution in a task

In Cocoon we have an Ant task for patching our config files. I'd like to extend this to be able to expand properties found in the patch files. How can I, in a Task, expand properties within a String? For example, if I have a string that says "${local.mounttable}", I want to replace it with the v

[PATCH] redundant quotes in runant.py

Hi, With a previous patch for runant.py I wrote to use the new ant-launcher.jar I accidentally introduced some redundant double quotes in the command to be executed. As it turns out these quotes are more than redundant, they're even wrong. If the user doesn't supply a target to run (i.e. run the

DO NOT REPLY [Bug 24743] New: - javadoc task fails for multiple source locations

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 24641] - java.util. ZipException while using jar task in ant 1.4.1 build

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 24641] - java.util. ZipException while using jar task in ant 1.4.1 build

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 24726] - apache-ant-1.6beta2-bin.tar is havnig unrequired files

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