+1 As guys who are always touting "standards", I think it behooves us to do everything we can to provide the community with a "best practices" example of using Maven to manage a rich, complex project, like Struts. (At least if doing that scratches someone's itch.)
Maven provides a standard framework for doing the things a project like ours needs to do. Not just for building, or dependency reuse, or reporting, or documentation, but for all of these things togther. If there are things that it doesn't do well, then we should help the Maven team to fix those problems, just like our users help us fix problems with Struts. I just gave a talk at the local users group about what we are doing with Struts these days. Several people button-holed me afterward about Maven. They've been having the exact same JAR management, build management, and project comprehension problems that we have. The great thing about Maven is that it's not only something that we can use, but something that our community can use too. Unlike anything we might cobble up ourselves, Maven is designed for reuse. Ditto for Subversion. I was stunned by how many Subversion questions there were. It's obvious that a lot of people can use a "compelling replacement for CVS", that is easy to install and plays well with Windows. I think by moving Struts to Subversion, we are leading by example, and may help a lot of teams down a better path. -Ted. On Sun, 10 Oct 2004 00:10:53 +0100, Marco Tedone wrote: > In my company we recently switched to Maven and Struts. Personally > I believe Maven is great, not only for the 'xdocs' facility, but > from a project management point of view. Its greatest benefit, IMO, > is to offer developers a common repository, via the dependency > mechanism, promoting integreation of jars versions and component > modularization. Amongst its other benefits, I certainly like the > fact that Maven promotes versioning stability (through the SNAPSHOT > option), it links to CVS repositories creating web reports about > developers activities and files checked in/out and the plugin > mechanism. If I want to use Ant, as Maven has been defined as an > 'Ant wrapper', I simply use ant scripts from within the Maven build > files. I believe that offering the possibility of building Struts > (and other open source projects) through Maven, will increase also > the projects' popularity and contributions. I remember that before > Maven, I often given up building from the source because of the > dependencies. Today I've downloaded version 1.2.4 of Struts, built > through Maven, and except from the build process hanging in the > middle a couple of times while downloading jars (I had to restart > it a couple of times), the built went on as smoothly as a piece of > cake. > > Marco > > > -------------------------------------------------------------------- > - 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]
