Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

2011-07-18 Thread Reinhard Nägele
I can switch back and forth between versions 2.1, 2.2, and 2.3. With 2.1 I don't get timestamped snapshots, with 2.2 and 2.3 I do get timestamped snapshots for artifacts that don't come from the reactor. The snapshots were deployed with Maven 3 to our Nexus server. I think, the fact that you

Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

2011-07-16 Thread Stephen Connolly
Brian, the changes in 2.2 were in the copy goal. the copy-dependencies goal is the one being used by Reinhart Reinhart, are you sure this is a change between 2.2 and 2.1, and nite some side-effect of having run the install phase on your dependencies locally? if the artifact is resolved from the

Dependency Plugin behavior changed to copy timestamped snapshot jars

2011-07-15 Thread Reinhard Nägele
Hi all, We use the dependency plugin's goal copy-dependencies in several projects. For snapshot dependencies, it would copy unique snapshot jars until version 2.1. Since version 2.2, the behavior has changed in that now timestamped snapshots are copied. I could not find this change anywhere

Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

2011-07-15 Thread Brian Fox
If the snapshot was resolved from a repo then it will be timestamped, if it came from the reactor or local repo, then it will be -SNAPSHOT. The plugin calls into the maven resolution logic so this is core maven behavior. In 2.2, resolution from the reactor was introduced for these goals,