Thanks, that is the most reasonable thing to do. Brining in a dependency on aether a great choice for my usage(s) though. Fortunately it should be pretty obvious in my case if this hack/assumption ever breaks.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Anders Hammar Sent: Tuesday, September 25, 2012 3:04 AM To: Maven Users List Subject: Re: maven3 snapshots in local repo I would recommend that you use Aether in that non-maven code to interact with remote and local repo. This is what Maven does and it will then ensure you don't run into issues. /Anders On Tue, Sep 25, 2012 at 12:13 AM, Tim Eck <[email protected]> wrote: > Using mvn 3.0.4, when a SNAPSHOT artifact is resolved from a remote > repo it seems that my local repository ends up with both a -SNAPSHOT > artifact and a timestamped version (the remote end has only timestamped versions). > I'm curious if I can rely on this behavior since I have other > (non-maven) code that interacts with my local maven repo. > > For example, from a dependency like so: > > <dependency> > <groupId>foo</groupId> > <artifactId>bar</artifactId> > <version>1.0.0-SNAPSHOT</version> > </dependency> > > I end up with with two identical jars in my local repo after > resolving > it: > > bar-1.0.0-20120924.201711-2.jar > bar-1.0.0-SNAPSHOT.jar > > I think the code in > org.eclipse.aether.internal.impl.DefaultArtifactResolver::getFile() > is responsible for making this additional copy > > > > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
