[jira] [Commented] (MWAR-422) specification of a classifier conflicts with primaryArtifact config
[ https://issues.apache.org/jira/browse/MWAR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836117#comment-16836117 ] Robert Scholte commented on MWAR-422: - Do you have a link to such a project? And it there are multiple javadoc and sourcefiles, to which of the war files do they belong to? > specification of a classifier conflicts with primaryArtifact config > --- > > Key: MWAR-422 > URL: https://issues.apache.org/jira/browse/MWAR-422 > Project: Maven WAR Plugin > Issue Type: Bug >Reporter: mike duigou >Priority: Major > Labels: has-patch > Time Spent: 10m > Remaining Estimate: 0h > > The documentation for the classifier configuration states "If given, the > artifact will be an attachment instead." which ignores the configuration > specified by the primaryArtifact config. > IMO, specification of a classifier should no cause a change in behaviour from > attaching main artifact vs attaching supplemental artifact. This behaviour > makes it impossible to use the deploy goal with a classifier specified > because there is no main artifact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-422) specification of a classifier conflicts with primaryArtifact config
[ https://issues.apache.org/jira/browse/MWAR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835990#comment-16835990 ] mike duigou commented on MWAR-422: -- Only war files (and source, javadoc) are being produced. The problem is that if you specify a classifier then there is no main artifact produced by the war plugin. An artifact with the specified classifier is created but it is treated as an attachment rather than as the main artifact. Since this artifact is not the main artifact it cannot be deployed as recent versions of the deploy plugin will deploy only the main artifact. > specification of a classifier conflicts with primaryArtifact config > --- > > Key: MWAR-422 > URL: https://issues.apache.org/jira/browse/MWAR-422 > Project: Maven WAR Plugin > Issue Type: Bug >Reporter: mike duigou >Priority: Major > Labels: has-patch > Time Spent: 10m > Remaining Estimate: 0h > > The documentation for the classifier configuration states "If given, the > artifact will be an attachment instead." which ignores the configuration > specified by the primaryArtifact config. > IMO, specification of a classifier should no cause a change in behaviour from > attaching main artifact vs attaching supplemental artifact. This behaviour > makes it impossible to use the deploy goal with a classifier specified > because there is no main artifact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-422) specification of a classifier conflicts with primaryArtifact config
[ https://issues.apache.org/jira/browse/MWAR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835883#comment-16835883 ] Robert Scholte commented on MWAR-422: - Sorry for the late response, but the list of open issues and PRs is long. bq. This behaviour makes it impossible to use the deploy goal with a classifier specified because there is no main artifact. This is intended. If you say the packaging of a project is war, it means the main artifact is a war. Otherwise the packaging should be pom if there's no main artifact. > specification of a classifier conflicts with primaryArtifact config > --- > > Key: MWAR-422 > URL: https://issues.apache.org/jira/browse/MWAR-422 > Project: Maven WAR Plugin > Issue Type: Bug >Reporter: mike duigou >Priority: Major > Labels: has-patch > Time Spent: 10m > Remaining Estimate: 0h > > The documentation for the classifier configuration states "If given, the > artifact will be an attachment instead." which ignores the configuration > specified by the primaryArtifact config. > IMO, specification of a classifier should no cause a change in behaviour from > attaching main artifact vs attaching supplemental artifact. This behaviour > makes it impossible to use the deploy goal with a classifier specified > because there is no main artifact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
