[
https://issues.apache.org/jira/browse/MJAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745400#comment-16745400
]
Robert Scholte commented on MJAR-254:
-------------------------------------
If you mean with "non Maven" artifacts 'files not generated by Maven', then it
is fully acceptable to upload them to the Maven repository. Tools like Ant or
Gradle can do that too.
However, it should follow the M2-layout, otherwise you cannot refer to it with
tags <dependency>, <plugin>, or <parent>.
Maven is not going to guess URLs: there's a clear definition how
groupId+artifactId+version+type (+classifier) is transformed to a URL.
> 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)
