You are actually hitting on a relatively common issue. Maven 1.x doesn't support multiple versions of plugins for example. Future versions will. So, once you start requiring specific versions, versus the latest and greatest always for all projects, then you can really have a lot of problems.
However! Maven can easily be bundled up and run by pointing MAVEN_HOME to the correct version for your project. So, if you have Maven A for Project A, and Maven B for Project B, then just make sure your MAVEN_HOME is pointing correctly, and just check Maven A and B into CVS with your project! Alternatively, and possibly better, is to use Continous Integration and nightly builds to verify that everything still builds, even when you haven't touched it in a while! That way as your Maven environment evolves, you know it still works with both old dormant code and new active code. Eric Pugh -----Original Message----- From: Laurent Petit [mailto:[EMAIL PROTECTED] Sent: Thursday, January 20, 2005 1:08 PM To: [email protected] Subject: Configuration Management with maven Hello, I'm searching the currently best available solution for this kind of problem, concerning Configuration Management and maven. In my company, we aim to manage correctly the whole configuration of our projects, including the tools we are using. Is is especially important with tools which are still changing quickly. Imagine I start a project now. I want to reference the exact version of my development environment : jdk version, tomcat version, maven & maven plugins version. So I write a document referencing all those versions. The goal of this document is to be able, if we have to re work on the project in a few months, to reinstall the development environment as quickly and accurately as possible (since I don't want to begin my re-work on the project to make my old maven scripts work with the maven 1.x.y last stable release, with potentially deprecated goals names, ...). I then am looking for a solution to automate the environment re-installation by some way. I thought of writing some custom goal in maven.xml, which could call the maven goal as many times as needed to upload the good versions of the plugins. But I think it would propagate such modifications out of my projects "area", since I think the plugin versions are installed for a given maven instance. So to my question : do you think there is a way to still have one maven instance and different plugin versions for different projects, or will I have to deal with as much maven instances as different projects configurations ? Not sure my question is very clear, but if you had the courage to read it, please feel free to answer :-) Thanks in advance, -- Laurent Petit --------------------------------------------------------------------- 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]
