ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20867] New: - The possibility of getting properties from ant scripts
Date Wed, 18 Jun 2003 12:06:44 GMT
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=20867>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20867

The possibility of getting properties from ant scripts

           Summary: The possibility of getting properties from ant scripts
           Product: Ant
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: t.kitynski@11interactive.com


Currently I can load properties via eg. <property/> or <loadproperties/> and 
this is good. Now, I have several projects that depend on each other in much 
sophisticated way that could <ant/> task to resolve. I put as many properties 
to external files as possible and I load them into via appriopriate task into 
ant scripts where necessary, but still I have to play with some properties in 
each build script. Let's say I want to include current velocity jar into each 
project---if there's newer version of it, I have to change every build file to 
point to correct file. Well, you can say I could have one properties file with 
all the paths and load it, but since I have different machines, I would like 
to spare myself the nescessity of setting absolute paths. Instead I rather set 
$VELOCITY_HOME and change it when new velocity appears, but using env 
variables is not possible in properties files, and again: loading just the 
current jar name and joining it within an ant script currently forces me to do 
it in every build.xml file.

So it would be great to have something, that have the possibility of setting 
props like now, use $ references to names, and that would allow include those 
properties in running script---this is exactly inversely to what <ant/> task 
does (in the meaning of passing properties).

I've looked at the faq and documentation, but I haven't found anything like 
that---if this actually IS implemented, then please let me know.

TIA

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message