I am absolutely agree with your opinion that unreproducability of build is a bad feature, but ...
1. Maven has a built-in mechanism of dependency version range (http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges). Using this you can set that the build will always include the last version of some artifact. That makes it absolutely unreproducable. So unreproducability doesn't contradict with the concepts of Maven and what I ask could be possible in it too. 2. What I want is absolutely reproducable. Maybe you didn't understand me. I want an artifact D to include last version of artifact A, but not among all versions of A but among versions that are present in D's full dependency tree. As dependency tree is not changed in time we get a reproducable build. At each moment of time (if artifacts from dependency tree are not changed) final D's build will include the same version of A. Moreover, what I want, I suppose, is much more reproducable and logical behaviour because using standard behaviour you depend very strongly on the order in which dependencies are declared. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4672834.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]
