[jira] [Closed] (MWAR-422) specification of a classifier conflicts with primaryArtifact config

["Robert Scholte (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MWAR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MWAR-422.
-------------------------------
      Assignee: Robert Scholte
    Resolution: Won't Fix

In case you don't have a main artifact, the packaging should be pom. However, then you'll loose the compiling, testing, etc. (this is something we need to fix with a newer modelVersion, I am aware of that).
What you could do now is using {{jar}} as packaging instead to benefit from the lifecycle. Next you'll need execution-blocks within the maven-war-plugin, specifying the {{war}} goal.
That's the closest you will get within the current limitations of Maven.
So I'll close this one as Wont Fix.

> 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
>            Assignee: Robert Scholte
>            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
(v8.3.4#803005)