Mark Hindess wrote:
1) As we discussed yesterday, I have submitted a jira to add a global property.

2) Yes, but there are several scripts that can kick things off.  At
the top-level with make/build.xml and make/build-test.xml.  But also
within each module directory with make/build.xml.

How about a user property file for ant?


So 2) is not trivial.  George's change modifies all of these.  My
patch modifies all of these so that a top-level property is defined
once (and can be overriden on the ant command line).

Regards,
 Mark.

On 4/13/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
idle curiosity... 1) why not make both 'source' and 'target' settable by
a property, and 2) educate me on ant - why couldn't this have been set
in a property in the script that kicked things off and have the value
propagate down?


[EMAIL PROTECTED] wrote:
Author: gharley
Date: Wed Apr 12 10:03:36 2006
New Revision: 393521

URL: http://svn.apache.org/viewcvs?rev=393521&view=rev
Log:
Temporary move to compile with "modern" compiler using the "jsr14" target until 
5.0 VM support becomes available.

[snip]

--
Mark Hindess <[EMAIL PROTECTED]>
IBM Java Technology Centre, UK.

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to