maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAR-254) The fix for MJAR-198 is incomplete: filename conflict not detected
Date Sun, 02 Sep 2018 19:28:00 GMT

    [ https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601659#comment-16601659
] 

ASF GitHub Bot commented on MJAR-254:
-------------------------------------

khmarbaise commented on issue #1: [MJAR-254] - Fixes filename conflict when producing 2 jars
without classifier
URL: https://github.com/apache/maven-jar-plugin/pull/1#issuecomment-417954127
 
 
   That would be great. I appreciate to see a fix for that and afterwards I appreciate to
merge it...

----------------------------------------------------------------
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:
users@infra.apache.org


> 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)

Mime
View raw message