You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike (JIRA)" <ji...@apache.org> on 2019/07/29 14:02:00 UTC
[jira] [Updated] (MSHADE-323) Flatten Maven Plugin conflicts with
Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike updated MSHADE-323:
------------------------
Description:
When using Flatten Maven Plugin in the same project with Maven Shade Plugin then the dependency reduced POM is _not_ flattened.
What i encountered that having flatten plugin configured according to [https://maven.apache.org/maven-ci-friendly.html], and having shade plugin configured with the default settings to produce uber jar the ${revision} variable remains and gets installed/deployed within the final pom, thus making the pom in the repository invalid.
It seems that both plugins transform original pom. And then what gets installed in the last one, which is the 'shades' one. I'm not sure that's a bug (in a sense that it is shade's fault).
See also [https://github.com/mojohaus/flatten-maven-plugin/issues/100]
was:
When using Flatten Maven Plugin in the same project with Maven Shade Plugin then the dependency reduced POM is _not_ flattened.
What i encountered that having shade plugin configured according to [https://maven.apache.org/maven-ci-friendly.html], and having shade plugin configured with the default settings to produce uber jar the ${revision} variable remains and gets installed/deployed within the final pom, thus making the pom in the repository invalid.
It seems that both plugins transform original pom. And then what gets installed in the last one, which is the 'shades' one. I'm not sure that's a bug (in a sense that it is shade's fault).
See also [https://github.com/mojohaus/flatten-maven-plugin/issues/100]
> Flatten Maven Plugin conflicts with Maven Shade Plugin
> ------------------------------------------------------
>
> Key: MSHADE-323
> URL: https://issues.apache.org/jira/browse/MSHADE-323
> Project: Maven Shade Plugin
> Issue Type: Bug
> Reporter: Mike
> Priority: Minor
>
> When using Flatten Maven Plugin in the same project with Maven Shade Plugin then the dependency reduced POM is _not_ flattened.
> What i encountered that having flatten plugin configured according to [https://maven.apache.org/maven-ci-friendly.html], and having shade plugin configured with the default settings to produce uber jar the ${revision} variable remains and gets installed/deployed within the final pom, thus making the pom in the repository invalid.
> It seems that both plugins transform original pom. And then what gets installed in the last one, which is the 'shades' one. I'm not sure that's a bug (in a sense that it is shade's fault).
> See also [https://github.com/mojohaus/flatten-maven-plugin/issues/100]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)