[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747243#comment-16747243
]
Archie Cobbs commented on MJAR-254:
-----------------------------------
Argh, well it's been so long since I actually ran into this problem that I
don't remember exactly how it came up.
And looking at it more... I think what I was trying to do can probably be done
with build-helper:attach-artifact.
Thanks for helping me figure this out. No need to rehash any further.
> The fix for MJAR-198 is incomplete: filename conflict not detected
> ------------------------------------------------------------------
>
> Key: MJAR-254
> URL: https://issues.apache.org/jira/browse/MJAR-254
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Archie Cobbs
> Assignee: Robert Scholte
> Priority: Minor
> Labels: up-for-grabs
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> See this comment on MJAR-198.
> In summary, the build should fail if the actual JAR file would get
> overridden, not if the classifier happens to be the same. That is, the
> conflict is at the actual filesystem level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
