It's possible your maven had cached some metadata that caused maven to not be able to locate the correct timestamp version.
On Thu, Sep 17, 2009 at 1:47 PM, Benson Margulies <[email protected]> wrote: > This seems to have been a nexus bug. > > I made some changes in how my mirrors were configured, and this problem > evaporated. > > > > > On Thu, Sep 17, 2009 at 10:22 AM, Olivier Lamy <[email protected]> wrote: > >> Hi, >> The snapshot url you are using and the stack trace you have could be >> very helpfull. >> >> 2009/9/17 Benson Margulies <[email protected]>: >> > I set out to use a snapshot of the maven-release-plugin. I added the >> > snapshot repo to the pluginRepositories, with snapshots set to true. >> > >> > Then I called out version 2.0-beta-10-SNAPSHOT as my release. I got an >> error >> > message from maven to the effect that it could not find the jar file. >> > >> > So I changed the version to call out the full timestamp version number, >> and >> > it worked. >> > >> > is this the intended behavior? >> > >> >> >> >> -- >> Olivier >> >> --------------------------------------------------------------------- >> 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]
