<snip>lots as I'm responding to specific notes</snip> > 3) Not keeping JARs in the repository. That is the one thing that bugs me > about > the Cocoon build infrastructure. There is a mountain of JAR files > that are needed in some contexts, but not others. You can't keep it > straight.
Last week I switched back from maven (because I could no longer work within it's sandbox) to ant. The big this for me was dependency resolution. In the end it's very easy using ant 1.6 see: http://blogs.codehaus.org/people/kevin/archives/2003/09/21/index.shtml#000168 <snip /> > Again, I am not pressing for Maven, but these are the features that we > get for free with it. Since it looks like we are using ANT, how do we > resolve these needs? Umm I'm not sure that this is the case. There is nothing I've seen or used with Maven that can't be done with ant 1.6 (import / subant / antlib etc). The bous is that you get to set the dependencies between build targets not mavne (which as can be seen from the latest set of issues with aspectj) can be very difficult to resolve. -k.
