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

Karl Heinz Marbaise updated MSHADE-187:
---------------------------------------
    Description: 
Using the following configuration:
{code}
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-shade-plugin</artifactId>
        <configuration>
          <artifactSet>
            <includes>
              <include>org.apache.maven.profiler:*</include>
              <include>org.apache.maven.plugins:*</include>
              <include>org.apache.maven.surefire:*</include>
            </includes>
            <excludes>
              <exclude>org.sonatype.plexus:*</exclude>
              <exclude>javax:*</exclude>
            </excludes>
          </artifactSet>
        </configuration>
        <executions>
          <execution>
            <goals>
              <goal>shade</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
{code}

Based on the docs:
{code}
Flag whether to generate a simplified POM for the shaded artifact. If set to 
true, dependencies that have been included into the uber JAR will be removed 
from the <dependencies> section of the generated POM. The reduced POM will be 
named dependency-reduced-pom.xml and is stored into the same directory as the 
shaded artifact. Unless you also specify dependencyReducedPomLocation, the 
plugin will create a temporary file named dependency-reduced-pom.xml in the 
project basedir.
{code}
The dependency reduced pom should be stored within target folder (where the 
shaded artifacts has been stored into) and not in the project basedir.

This is the documentation of the dependencyReducedPomLocation parameter:
{code}
     * Where to put the dependency reduced pom.
     * Note: setting a value for this parameter with a directory other than 
${basedir} will change the value of
     * ${basedir} for all executions that come after the shade execution. This 
is often not what you want.
     * This is considered an open issue with this plugin.
{code}


  was:
Currently i'm getting the following messages during a build with 
maven-shade-plugin:
{noformat}
[INFO] Dependency-reduced POM written at: 
/Users/kama/ws-git/maven-test-profiler/dependency-reduced-pom.xml
[INFO] Dependency-reduced POM written at: 
/Users/kama/ws-git/maven-test-profiler/dependency-reduced-pom.xml
{noformat}
This is the configuration which produces this:
{code}
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-shade-plugin</artifactId>
        <configuration>
          <artifactSet>
            <includes>
              <include>org.apache.maven.profiler:*</include>
              <include>org.apache.maven.plugins:*</include>
              <include>org.apache.maven.surefire:*</include>
            </includes>
            <excludes>
              <exclude>org.sonatype.plexus:*</exclude>
              <exclude>javax:*</exclude>
            </excludes>
          </artifactSet>
        </configuration>
        <executions>
          <execution>
            <goals>
              <goal>shade</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
{code}

Based on the docs:
{code}
Flag whether to generate a simplified POM for the shaded artifact. If set to 
true, dependencies that have been included into the uber JAR will be removed 
from the <dependencies> section of the generated POM. The reduced POM will be 
named dependency-reduced-pom.xml and is stored into the same directory as the 
shaded artifact. Unless you also specify dependencyReducedPomLocation, the 
plugin will create a temporary file named dependency-reduced-pom.xml in the 
project basedir.
{code}
The dependency reduced pom should be stored within target folder (where the 
shaded artifacts has been stored into) and not in the project basedir.


> Duplicate WARNINGs during build
> -------------------------------
>
>                 Key: MSHADE-187
>                 URL: https://issues.apache.org/jira/browse/MSHADE-187
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 3.0
>
>
> Using the following configuration:
> {code}
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-shade-plugin</artifactId>
>         <configuration>
>           <artifactSet>
>             <includes>
>               <include>org.apache.maven.profiler:*</include>
>               <include>org.apache.maven.plugins:*</include>
>               <include>org.apache.maven.surefire:*</include>
>             </includes>
>             <excludes>
>               <exclude>org.sonatype.plexus:*</exclude>
>               <exclude>javax:*</exclude>
>             </excludes>
>           </artifactSet>
>         </configuration>
>         <executions>
>           <execution>
>             <goals>
>               <goal>shade</goal>
>             </goals>
>           </execution>
>         </executions>
>       </plugin>
> {code}
> Based on the docs:
> {code}
> Flag whether to generate a simplified POM for the shaded artifact. If set to 
> true, dependencies that have been included into the uber JAR will be removed 
> from the <dependencies> section of the generated POM. The reduced POM will be 
> named dependency-reduced-pom.xml and is stored into the same directory as the 
> shaded artifact. Unless you also specify dependencyReducedPomLocation, the 
> plugin will create a temporary file named dependency-reduced-pom.xml in the 
> project basedir.
> {code}
> The dependency reduced pom should be stored within target folder (where the 
> shaded artifacts has been stored into) and not in the project basedir.
> This is the documentation of the dependencyReducedPomLocation parameter:
> {code}
>      * Where to put the dependency reduced pom.
>      * Note: setting a value for this parameter with a directory other than 
> ${basedir} will change the value of
>      * ${basedir} for all executions that come after the shade execution. 
> This is often not what you want.
>      * This is considered an open issue with this plugin.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to