[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744503#comment-16744503
]
Robert Scholte commented on MJAR-254:
-------------------------------------
This is one of the main reasons why why started to remove finalName from the
configuration. The only reason to use a custom final name is when you want to
build it on your own system and copy it directly from your target directory to
some other location (due to filename policies or whatever).
If you want to make this jar available for other projects via a repository,
Maven will upload it according the M2-layout, so the coordinate resolution
works when defined as dependency, parent of plugin in any pom.xml
> 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
> Priority: Minor
> Labels: up-for-grabs
> Time Spent: 10m
> 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)
