[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595516#comment-16595516
]
ASF GitHub Bot commented on MJAR-254:
-------------------------------------
Maastiff opened a new pull request #1: [MJAR-254] - Fixes filename conflict
when producing 2 jars without classifier
URL: https://github.com/apache/maven-jar-plugin/pull/1
Hello,
I provided a failing test for this issue, I will try to going further to
develop the fix.
Done @Hackergarten in Paris with @hboutemy (thanks for his help) ;)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
>
> 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)
