[
https://issues.apache.org/jira/browse/MSHARED-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636492#comment-16636492
]
Robert Scholte commented on MSHARED-760:
----------------------------------------
If the packaging is {{pom}} there should be no issue. This seems to be a case
the lifecycle bindings for some packaging are abused to create one or more
attachments, without delivering a main artifact.
In my opinion they should have used pom, because packaging mainly describes the
result of this pom. For model 5.0.0 there are proposals to separate
lifecycle-bindings and packaging for usecases like this and the other way
around (lifecycle-bindings for pom, but packaging war, because it is create by
some special plugin), but for now I wouldn't start allowing it.
> Do not fail if no main artifact has been set, but attachments existing
> ----------------------------------------------------------------------
>
> Key: MSHARED-760
> URL: https://issues.apache.org/jira/browse/MSHARED-760
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-artifact-transfer
> Affects Versions: maven-artifact-transfer-0.11.0
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Priority: Blocker
> Fix For: maven-artifact-transfer-0.11.0
>
>
> We should not fail if no main artifact has been set but attachments do exist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
