On Thu, June 28, 2007 3:36 pm, martin_CY wrote: > I just wonder how I should proceed. Because we really don't like dealing > with all the jars in the lib/ !! and also having the main application's > jars > versioned and in an internal repository would make life a lot easier for > the > web/Tapestry project to handle its dependencies on the main project.
Proceed with baby steps - having got to the advanced stage of a very similar task on another project, it's quite a journey. The reason moving to maven is quite involved is because maven enforces quite a rigorous project discipline onto your project: Proper version number management, a proper release process, formal ways of firing off test suites. It can take quite a bit of time to clear out the various shortcuts that people stick into ant scripts, and to convince people to be more disciplined during development. The end goal however is worth it: Once maven works, and as long as people work with maven and not against it, project releases become very smooth and trouble free. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
