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, previously they would always go to the repository, this could be why you see a change in the new version. On Fri, Jul 15, 2011 at 5:28 AM, Reinhard Nägele <reinhard.naeg...@mgm-tp.com> wrote: > 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 in the release notes. In fact, it is > not documented at all, what the correct behavior is supposed to be. Is > anyone aware of this change? Has it happened on purpose or by accident? > Anyway, I'd really like to get the old behavior back. I think this should be > configurable. > > Any opinions or insights? > > Thanks, > Reinhard > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
