[jira] [Commented] (MSHADE-36) Add option to include dependency reduced POM instead of original one

["John Dimeo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSHADE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681000#comment-17681000 ] 

John Dimeo commented on MSHADE-36:
----------------------------------

Thanks for the work on this, but something very very strange just happened: one of my child modules of one of my multi-module projects seemigly used the new dep reduced POM as it's "real" POM and it then removed all transitive dependencies (without me telling the plugin to do so) for downstream Maven builds. I'm not sure how or why it happened, but just a heads up.  From my perspective, I just updated the Maven shade plugin and transitive dependencies stopped working- no configuration was changed. The workaround is to set {{useDependencyReducedPomInJar}} back to false (since thankfully no one downstream is using it).

> Add option to include dependency reduced POM instead of original one
> --------------------------------------------------------------------
>
>                 Key: MSHADE-36
>                 URL: https://issues.apache.org/jira/browse/MSHADE-36
>             Project: Maven Shade Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.1
>            Reporter: Mark Hobson
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.3.0
>
>
> The dependency reduced pom needs to replace the packaged pom at:
> META-INF/maven/<groupId>/<artifactId>/pom.xml
> This will allow tools that use this metadata to read the correct shaded dependencies (e.g. maven-runtime).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)