@benjamin There are several drawbacks with the maven-dependency-plugin:purge-local-repository:
- Performances slowdown if used systematically, i.e. included in project's pom or worse super pom, due to the downloads from the remote. One benefit of upgrading to maven 3 for us is the performance improvement, this will kill it. - According to Maven 3 incompatibilities the way dependencies are analyzed has changed and the dependency plugin has not yet been updated, potentially resulting in different set of artifacts being purged than those build https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution. I am assuming that all the maven-dependency-plugin goals share the same resolution mechanism as the tree one. - Leaving it up to the developers, at the expense of putting on them a new thing they didn't had to bother when using Maven 2, at least not so often. Not a selling point for Maven 3 adoption. @Jörg Just to clarify, the timestamp artifacts don't end with -SNAPSHOT but with the timestamp like A-1.0.0-20110302.160157-17.jar. -- View this message in context: http://maven.40175.n5.nabble.com/Issue-with-mvn3-timestamp-snapshots-being-downloaded-in-local-repository-tp3408008p3408225.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
