[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745426#comment-16745426
]
Archie Cobbs commented on MJAR-254:
-----------------------------------
Sorry for the ambiguity. What I meant by "non Maven" was "generated by Maven
but downloaded by something else".
In my case, I want to use Maven to build and deploy stuff because it's a great
tool, but I also want to access those deployed files in multiple ways and with
different clients, some of which are not Maven. So it's not a problem if the
extra <fileName> artifacts are effectively unreachable to a Maven client,
because I'll be accessing them with something else. But I do want to build and
deploy those extra <fileName> artifacts with Maven because that's my build tool
and the artifacts are all related. Hope this makes sense.
> 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)
