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 35464] - Add a dry run mode
Date Wed, 22 Jun 2005 16:00:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35464>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35464





------- Additional Comments From francois.robert@unisys.com  2005-06-22 18:00 -------
Thanks for your (fast !) answers and suggestions. I will definitely have a look 
at Maven, to see whether it can help me. 

Regarding <import>. Can you elaborate a bit more ? Are you suggesting to write a 
top level ant file that call others via <import> ?  Or did I miss the point ? (I 
want to avoid writting -and maintaining...- a top-level build file, because it's 
so easy do get it out-of-synch with the child projects)

The point is that the projects have no direct knowledge of each other. 
Dependencies are basically expressed indirectly, through the content of the 
"classpath" settings.

Ho. And then there is Eclipse. At some point in the future, I want to be able to 
check that all build.xml are in synch with Eclipse projects (same classpath, 
basically...). Admitedly, this has nothing to do directly with a "dry-run" 
feature per se. It may however help you frame the business use case I have in my 
hands...

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message