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 [EMAIL PROTECTED] 2005-06-22 17:26 ------- I'm not sure that this can be done. It isnt enough to parse the file, you have to know the output of every single task in the system. In make (i.e. make -n) the output is there, as it is just walking the dependency chain you specify by hand. In ant, things work it out for themselves, based on (chained) input files. you need to know the output of all predecessors before you can predict what the next components will do, something that is done using the filesystem as a persistent state communication mechanism. Now Maven, that does have a more explicit model of deliverables, and you may want to look at that to see if it works on your (seemingly large/complex) project. For reference, I use their ant tasks and have sub projects deploy into the maven repository on a local machine, as a way of decoupling projects from each other. I would also encourage looking at the <import> task in Ant1.6+, which lets you share stuff across projects. Having many sub projects does not imply lots of duplicated code. If you can have everything share the same build files, you will stay in control. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
