[EMAIL PROTECTED] wrote: > > The problem is that maven assumes that the -SNAPSHOT is the newest, not > the oldest version available. > > You obviously have projects that declare dependencies on just -SNAPSHOT, > but want the latest *dated* version to be used. So I suggest you delete > the original -SNAPSHOT version, or rename it to have an appropriate date > suffix. > The problem is that when I install new versions of that jar, they don't get picked up by the build - although the -SNAPHSOT version is NOT the newest anymore then.
And this all has to work without deleting anything from the internal or local repositories - otherwise the problem will reoccur whenever new snapshots are created. I believe my understanding is correct: here's a quote from the "Better builds with Maven book: "You'll see that it is treated differently than when it was installed in the local repository. The filename that is used is similar to proficio-api-1.0-20060211.131114-1.jar. In this case, the version used is the time that it was deployed (in the UTC timezone) and the build number. If you were to deploy again, the time stamp would change and the build number would increment to 2. This technique allows you to continue using the latest version by declaring a dependency on 1.0- SNAPSHOT, or to lock down a stable version by declaring the dependency version to be the specific equivalent such as 1.0-20060211.131114-1." Papapara Tudu -- View this message in context: http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15711423.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]
