[
https://issues.apache.org/jira/browse/MSHADE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324190#comment-17324190
]
Robert Scholte commented on MSHADE-382:
---------------------------------------
Now I see what's happening. Who said you couldn't be creative with Maven :).
So they are rewriting the bindings to the jar-lifecycle, and that causes the
issue.
I need to think what would be a better solution here.
But it is already possible with the following:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<executions>
<execution>
<id>default-shade</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
{code}
Maybe a little bit more lines in the pom, but the build is more efficient,
because it doesn't have to initialize the ShadeMojo.
> Add an option to skip execution
> -------------------------------
>
> Key: MSHADE-382
> URL: https://issues.apache.org/jira/browse/MSHADE-382
> Project: Maven Shade Plugin
> Issue Type: Improvement
> Affects Versions: 3.2.4
> Reporter: Andres Almiray
> Priority: Major
>
> It'd be great to have a property for skipping execution, such as
> `maven.shade.skip`. Useful when a parent has setup shading but a child would
> like to skip it for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
