[
https://jira.codehaus.org/browse/MSHADE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332382#comment-332382
]
Richard Sand commented on MSHADE-134:
-------------------------------------
the patch I submitted in 154 solves this, sorry for the duplicate
> Shade plugin does not seem to be aware of the classifier setting for the jar
> plugin
> -----------------------------------------------------------------------------------
>
> Key: MSHADE-134
> URL: https://jira.codehaus.org/browse/MSHADE-134
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Thomas Dudziak
>
> When using the classifier configuration for the jar plugin, e.g.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.4</version>
> <configuration>
> <classifier>foo</classifier>
> </configuration>
> </plugin>
> then the shade plugin (in both attach or replace modes) complains about a
> missing main artifact:
> [ERROR] The project main artifact does not exist. This could have the
> following
> [ERROR] reasons:
> [ERROR] - You have invoked the goal directly from the command line. This is
> not
> [ERROR] supported. Please add the goal to the default lifecycle via an
> [ERROR] <execution> element in your POM and use "mvn package" to have it
> run.
> [ERROR] - You have bound the goal to a lifecycle phase before "package".
> Please
> [ERROR] remove this binding from your POM such that the goal will be run in
> [ERROR] the proper phase.
> [ERROR] - You removed the configuration of the maven-jar-plugin that produces
> the main artifact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
