Niels Basjes created MSHADE-440:
-----------------------------------

             Summary: Expanded properties in profiles in DRP
                 Key: MSHADE-440
                 URL: https://issues.apache.org/jira/browse/MSHADE-440
             Project: Maven Shade Plugin
          Issue Type: Bug
            Reporter: Niels Basjes


If you have a profile with the {{{}$\{project.basedir{}}}} in the configuration 
of a plugin IN that profile.

Then when you run maven-shade with that profile active the  
{{{}$\{project.basedir{}}}}  will be expanded to the full value in some places 
of the generated DRP.

If you have something like this in the pom.xml 

{code:xml}

  <profiles>
    <profile>
      <id>testProfile</id>
      <properties>
        <prop>CHECK Inside profile ${project.basedir}.</prop>
      </properties>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-clean-plugin</artifactId>
            <executions>
              <execution>
                <id>CHECK Inside profile ${project.basedir}.</id>
                <configuration>
                  <testOutputDirectory>CHECK Inside profile 
${project.basedir}.</testOutputDirectory>
                </configuration>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>
{code}

then the DRP will have the project.basedir value replaced with the actual path.
This ONLY happens if it is in an profile that was active during while shade was 
running.


 



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

Reply via email to