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).
Regards, -Scott > -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 22, 2006 9:55 AM > To: Jetspeed Users List > Subject: Re: RFC: J2 Build System > > Dr. Michael Lipp wrote: > > David Sean Taylor wrote: > >> As for using Maven-2 in the Jetspeed build, I think there is still a > >> valid argument to take this approach. As suggested more than once on > the > >> dev list, maybe the problem isn't Maven, its really us. Anyone at > >> Mergere want to send the Jetspeed team and users to a Maven-2 training > >> session? > > > > But that's the point: nobody in our organization has ever required or > > requested an Ant training! > > > > And even if the Jetspeed team can handle Maven-2 easily after having > > been trained (and I doubt it, I mean, these are really capable people > > that have obviously gone to great lengths to get things going; what > > crucial knowledge can they gain in a training), what happens to the rest > > of us? > > > Hmm, now I think the best build system should not be visibile to the > user which > means you just invoke "build.bat/build.sh" and are done - and this is > regardless of using either ant or maven or whatever. And I think this > should be possible with both ant or maven. > The only real difference I see from a user pov is that maven requires a > network connection the first time you build; but as someone already > pointed out this is only required if you want to build maven from the > source. For releases, jetspeed will provide binary versions anyway. > > Personally, I would try to go the m2 way. > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
