DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24641.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24641.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24743.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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
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.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24743.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
[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!
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:
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24712.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23913.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[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
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
Last week, I sent a questionary about
namespace support in ant 1.6.
http://marc.theaimsgroup.com/?l=ant-devm=106848848930806w=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
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
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 properties, if I
OK, how do we want to implement macrodef attributes:
[X] as textual substitution
[ ] as real Ant properties
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 14 Nov 2003, Jan Materne [EMAIL PROTECTED] wrote:
macrodef name=macro
attribute name=one/
attribute name=two default=${one}/
/macrodef
macro one=hello/
I don't think we should need any special cludges just to support this
usecase. 8-)
Give two a completely bogus, impossible
Here´s my build file, i think that its ok. And if I did wrong,
jspc output should give a error message not a stacktrace.
?xml version=1.0?
!--/--
projectname=osctrl
basedir=/tmp
On Monday 17 November 2003 16:11, Matt Benson wrote:
--- peter reilly [EMAIL PROTECTED] wrote:
For example:
project xmlns:antcontrib=antlib:net.sf.antcontrib
xmlns:acme=antlib:org.acme.anttasks
target name=show
antcontrib:if
antcontrib:or
Matt Benson wrote:
--- peter reilly [EMAIL PROTECTED] wrote:
For example:
project xmlns:antcontrib=antlib:net.sf.antcontrib
xmlns:acme=antlib:org.acme.anttasks
target name=show
antcontrib:if
antcontrib:or
antcontrib:equals arg1=yes arg2=${prop}/
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24756.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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]
From: peter reilly [mailto:[EMAIL PROTECTED]
Yes, this is std xml (not visible from ant processing code):
project xmlns:antcontrib=antlib:net.sf.antcontrib
xmlns:ant=antlib:org.apache.tools.ant
xmlns:acme=antlib:org.acme.anttasks
target name=show
if
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):
project xmlns:antcontrib=antlib:net.sf.antcontrib
xmlns:ant=antlib:org.apache.tools.ant
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for project and target 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
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 project and target does not matter?
Conceptually they are part of the Ant XML dialect to me,
so
Dominique Devienne wrote:
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for project and target 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
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 project and target does not matter?
Conceptually they are part of the Ant XML dialect to me,
On Monday 17 November 2003 15:57, Stefan Bodewig wrote:
On Fri, 14 Nov 2003, peter reilly [EMAIL PROTECTED] wrote:
An example:
target name=s
macrodef name=show
element name=x/
sequential
property name=inmacro value=Set in macro/
x/
/sequential
OK, how do we want to implement macrodef 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?
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
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 thing
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 project and target does not matter?
Conceptually they are part of the Ant XML
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24761.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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 TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24761.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[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
41 matches
Mail list logo
