Scott T Weaver wrote: > The problem is most users will not have Maven installed, so a script file > will be of no use to them until they have manually installed Maven. Even if > they had it installed, there where instances where certain versions of Maven > broke the build. Now you have shackled the user with having to upgrade > Maven along with building your project. I guess I have a bad taste in mouth > with the fact that it seemed that there was a lack of concern for the > end-users on the part of the Maven team (severe lack of documentation, build > scripts not working from one minor version to the next). Maybe all this has > been resolved in M2, maybe not. From what I am hearing from Randy and > David, it still seems that we need ugly hacks just to get simple things > working in M2. Personally I have had my fill of messing with builds. I > have a great confidence in Randy and David's ability to evaluate the > merits/shortcomings of M2 with regards to building J2's core. As far as > integration, I will stick with my ant scripts which work beautifully (don't > fix it if it ain't broke). > Yes, you're absolutely right - we are going through the same pain in the Cocoon project (trying to move from Ant to M2). I guess we have similar problems: compiling code and managing dependencies (inner project or to external jars) is working great with m2 - we had to write very complicated ant scripts which where very hard to maintain. So this is definitly a big step forward. But everything else going beyond this (compiling and creating a jar) seems to be a pain in m2 and even after several weeks we don't have a solution yet (which is not only because it's complicated but currently noone has time to work on this, so it's perhaps not m2's fault). Now, for the release we are planning (but have not decided) to perhaps even ship a version of M2 with Cocoon (and the next step of course will be to ship the JDK with Cocoon as well - but fortunately this is currently not allowed :) ). So all the end user has to do, is download the release, extract it and invoke the build script. Of course this is only theory, but it solves at least the problem that users are using a wrong m2 version. We had the same problems actually with Ant. Cocoon required Ant 1.6.x and users had 1.5 installed - so we bundled Ant with Cocoon and solved the issues this way. So all I'm trying to say is, that you can run into similar problems with Ant as well.
Currently I don't know enough about j2 to give a helpfull opinion, but the maven build so far always worked great for me :) And it will be interesting to see what j2 is doing, so perhaps we can learn something for Cocoon :) Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
