On Fri, 17 Sep 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote: > I can foresee the not too distant future when these Ant sub-projects > will start having dependencies between each other, so compiling them > would either require (Maven + ibiblio (or an ASK equivalent)) or > have the sub-project check in the JARs they depend on (Uhhh!).
Personally I'm known to be part of the "one big source tree, multiple jars" camp, so I wouldn't see any JARs in the SCM system since every lib would compile against the sources of the other libs directly. A middle ground could be a Jakarta Commons like tree of antlibs that could compile against each other if needed, but could get built stand-alone if so desired. > What I had in mind was more an antlibs/ sub-dir in Ant, which the > Ant build file could easily recurse into to build once it's own > build is complete. I can imagine that antlibs would require third party libraries that might or might not be present. But yes, I agree with the general idea, I might just want to decouple it from Ant itself. We probably can take an Ant installation of a recent version as something that is a requirement for Antlib developers. > I already have the extension to subant to dynamically infer the > build order to use to call the sub-projects in a flexible way (all > you need is some XML file stating the sub-project's dependencies). A <buildpath> task is on my TODO list, unfortunately I barely manage to keep track of the items I have to add, not to speak of addressing them. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
