[
https://issues.apache.org/jira/browse/MSOURCES-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSOURCES-124:
-------------------------------------
Priority: Minor (was: Major)
> Sources and test sources should have separate artifact types
> ------------------------------------------------------------
>
> Key: MSOURCES-124
> URL: https://issues.apache.org/jira/browse/MSOURCES-124
> Project: Maven Source Plugin
> Issue Type: Bug
> Affects Versions: 3.2.1
> Reporter: Peter De Maeyer
> Priority: Minor
>
> Imagine a project that has main and test sources, resulting in 4 artifacts:
> ||Artifact||Type||Default classifier||
> |Main JAR|"jar"| |
> |Test JAR|"test-jar"|"tests"|
> |Main sources|"java-source"|"sources"|
> |Test sources|"java-source"|"test-sources"|
> Both sources and test sources have have type "java-source".
> As a result, it is not possible to distinguish the sources from the test
> sources based on type alone.
> The classifier can be used to make that distinction, but the classifier can
> be overridden to be anything while the type is fixed.
> To fix this, I suggest to introduce a separate type "java-test-source" for
> test sources.
> The only drawback of that is backward compatibility and impact on other
> plugins which might use hard-coded types.
> On the other hand, attaching test sources is not often used, so I don't
> expect it to break a lot, and it will be better in the long run.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
