Dependency Plugin behavior changed to copy timestamped snapshot jars

[Reinhard Nägele <re...@mgm-tp.com>]

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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

[Reinhard Nägele <re...@mgm-tp.com>]

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 get timestamped snapshops depending on whether the artifacts come 
from the reactor or the local repo is something a user wouldn't expect.

I don't think switching to the copy goal is an option. The copy goal 
copies explicitly specified artifacts, whereas I want all dependencies 
to be copied. Or am I missing something here?

Thanks,
Reinhard


Am 16.07.2011 09:08, schrieb 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 reactor or the local repo it will be
> -snapshot if resolved from a remote repo which has unique versions true, or
> maven 3 was used to deploy, it will be the timestamp.
>
> if the filename is critical to you use the copy goal instead as, since 2.2
> that now resolves from the reactor and so can be used in all cases too
> (whereas prior to 2.2 if it was a dependency on a reactor module you would
> have had to use copy-dependencies)
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 16 Jul 2011 00:59, "Brian Fox"<br...@infinity.nu>  wrote:
>> 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
>> <re...@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-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

[Stephen Connolly <st...@gmail.com>]

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 reactor or the local repo it will be
-snapshot if resolved from a remote repo which has unique versions true, or
maven 3 was used to deploy, it will be the timestamp.

if the filename is critical to you use the copy goal instead as, since 2.2
that now resolves from the reactor and so can be used in all cases too
(whereas prior to 2.2 if it was a dependency on a reactor module you would
have had to use copy-dependencies)

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 16 Jul 2011 00:59, "Brian Fox" <br...@infinity.nu> wrote:
> 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
> <re...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Re: Dependency Plugin behavior changed to copy timestamped snapshot jars

[Brian Fox <br...@infinity.nu>]

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
<re...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org