I don't have a problem with tossing the Maven stuff. However, I believe we do have some Maven mavens in our midst who likely feel otherwise. This might sound odd, but perhaps, if we do have people who are interested in actively pursuing Maven, we should move the Maven stuff to contrib until such time as it provides a working replacement for our Ant build system?
My preference for Maven goes back to two primary features: 1) automatic dependency resolution, and 2) automatic project configuration in most major IDEs
That, and the fact that we had much more success using it as our team project management tool than we ever had with Ant, for whatever reasons.
My distaste for Ant in struts goes primarily back to what I consider a barbarically complicated build.properties file, particularly regarding dependencies. If that were manageable (as Martin alludes it might be), then I might not care much.
I don't really see how we can put Maven in "contrib" when its object is to work on the files in "core". I suppose it's theoretically possible, but it seems like a waste of energy.
At 11:36 AM -0500 12/9/04, James Mitchell wrote:
What's even more confusing is how different the maven project jar dependencies are vs the ant jar for the SAME PROJECT. Can you say CLEAN UP TIME?
See, this is a plus for Maven -- one file under CVS control is kept accurate with build dependencies; on the other hand, the current mechanism for using a sample build.properties file means that Ant dependencies aren't automatically kept up to date; you have to notice a change to the sample build.properties and then update your copy accordingly. I can imagine a way to achieve this with Ant, but we're not doing it now.
Is there any interest in cleaning some of this up?
Can we remove all the maven build stuff? Since:
a) Our Maven build does nothing except build a source and binary dist of struts.jar
b) Our ant build does everything that needs to be done (and then some)
c) Craig does the nightly builds and has no interest in changing to maven
"all the maven build stuff" boils down to three files (project.xml, project.properties, and maven.xml) and some lines in build.properties. It doesn't seem that onerous to me.
That said, I'm more interested in spending my limited time on 1.3 development than Maven, so I'm not sure I'm the one who could make Maven do everything you wish it would, and like you say, it won't replace Ant anyway. So I'd be -0 on removing it.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
