[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744521#comment-16744521
]
Archie Cobbs commented on MJAR-254:
-----------------------------------
{panel}
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.
{panel}
That seems like an overly-strong assertion. Seems like there are plenty of
use-cases where someone might want to deploy additional "non Maven" artifacts
to a Maven repo. Are you saying that should be illegal? If so, why?
> 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)
