Ralph Goers wrote:
Maybe this won't strike you as strange but it did me. I ran a mvn install on a project using 2.0.9. In the course of that maven-project-2.0, maven-project-2.0.6, maven-2.0.7, and maven-project-2.0.9 were downloaded, installed into the local repo and then used in the build. As you would expect this is due to the use of the various plugins used during the build. Knowing what I know about maven I understand why this us. But the question remains, doesn't this just seem wrong? Shouldn't maven 2.0.9 only use maven 2.0.9 jars?
One thing we could do to at least minimize the confusion, is to synchronize the versions of dependencies on Maven artifacts in a project.
Say that we have plugin A that has a prerequisite of Maven 2.0.6. Then all Maven dependencies in plugin A, that are included in the Maven core, should be set to version 2.0.6. Then at least only artifacts of that particular Maven version is downloaded when plugin A is executed.
-- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
