You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "nielsbasjes (via GitHub)" <gi...@apache.org> on 2023/03/24 22:31:35 UTC

[GitHub] [maven-shade-plugin] nielsbasjes commented on pull request #183: [MSHADE-440] Reproduce problem in IT.

nielsbasjes commented on PR #183:
URL: https://github.com/apache/maven-shade-plugin/pull/183#issuecomment-1483515447

   To clarify the problem I have created a reproduction in the form of an IT test for the project.
   
   This reproduction has a 3 elements in 3 places: "outside of any profile", "in an INactive profile", "in an ACTIVE profile".
   In some of the places in the active profile the project.basedir is expanded to the full value in the dependency-reduced-pom.xml.
   
   Summary of the lines that are present in the generated DRP in my reproduction:
   
   <prop>CHECK Outside profile ${project.basedir}.</prop>
   <prop>CHECK Inside inactive profile ${project.basedir}.</prop>
   <prop>CHECK Inside active profile ${project.basedir}.</prop>
   
   <id>CHECK Outside profile ${project.basedir}.</id>
   <id>CHECK Inside inactive profile ${project.basedir}.</id>
   <id>CHECK Inside active profile /home/runner/work/maven-shade-plugin/maven-shade-plugin/target/it/MSHADE-440-DRP-variables-in-profile.</id>
   
   <testOutputDirectory>CHECK Outside profile ${project.basedir}.</testOutputDirectory>
   <testOutputDirectory>CHECK Inside inactive profile ${project.basedir}.</testOutputDirectory>
   <testOutputDirectory>CHECK Inside active profile /home/runner/work/maven-shade-plugin/maven-shade-plugin/target/it/MSHADE-440-DRP-variables-in-profile.</testOutputDirectory>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org