Am 02/01/17 um 11:22 schrieb Stephen Connolly:
> On 1 February 2017 at 10:15, Karl Heinz Marbaise <[email protected]> wrote:
> 
>> Hi,
>>
>> On 01/02/17 10:50, Stephen Connolly wrote:
>>
>>> But doesn't the shade plugin want to do exactly that... namely attach
>>> the shaded jar *to replace* the jar attached by the jar plugin?
>>>
>>
>> Yes but if the maven-source-plugin does the same and attach a source
>> package which means you have two artifacts being attached with the same
>> name...
>>
>> This can in the end result in build failures during a release build where
>> those artifacts are being transfered to repo managaer which than blocks for
>> the second artifact which is already been there...
>>
>> The install plugin will simply install the same artifact a second time and
>> overwrites on HD so no problem...but deploy plugin will try to upload the
>> same artifact twice...
>>
> 
> Yes so the bug was where the attach artifacts with the same coordinates as
> an already attached artifact *appends* rather than updating

That's what had changed and what lead to the issues Karl-Heinz
describes. I just restored the old behaviour (replace instead of append
but log a warning instead of doing that silently). During working on
that, I found out about various issues regarding this and thought
restoring the former behaviour with logging a warning is something we
can do without breaking too much. Here are the issues I found related to
that:

+     * @see https://issues.apache.org/jira/browse/MNG-5868
+     * @see https://issues.apache.org/jira/browse/MNG-5387
+     * @see https://issues.apache.org/jira/browse/MNG-4013
+     * @see https://issues.apache.org/jira/browse/MNG-3119

It's really two different use cases:

o Replace an existing artifact (and fail the build if nothing to replace
is found).
o Attach an artifact (and fail the build if that artifact already is
attached).

Regards,
-- 
Christian


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to