You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2019/01/16 22:40:00 UTC

[jira] [Closed] (MJAR-254) The fix for MJAR-198 is incomplete: filename conflict not detected

     [ https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MJAR-254.
-------------------------------
    Resolution: Invalid
      Assignee: Robert Scholte

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