[ https://issues.apache.org/jira/browse/MINVOKER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958451#comment-17958451 ]
Olivier Lamy commented on MINVOKER-293: --------------------------------------- This project has moved from Jira to GitHub Issues. This issue was migrated to [apache/maven-invoker-plugin#519|https://github.com/apache/maven-invoker-plugin/issues/519]. Please visit the GitHub issue to view further activity, add comments, or subscribe to receive notifications. > Profiles are passed to invoked executions > ----------------------------------------- > > Key: MINVOKER-293 > URL: https://issues.apache.org/jira/browse/MINVOKER-293 > Project: Maven Invoker Plugin (Moved to GitHub Issues) > Issue Type: Bug > Affects Versions: 3.0.1, 3.2.2 > Reporter: Zbigniew Lis > Priority: Major > Attachments: maven-invoker-profile-inheritance.zip > > > If you run "mvn generate-resources -PmyProfile" on a project that *uses* > maven-invoker-plugin, then myProfile is passed to whatever execution you have > configured in this plugin *in addition* to what is configured in plugin > configuration, or in invoker.properties file. > To reproduce it using attached project: if you run "mvn generate-resources > -PmyProfile" on "maven-invoker-profile-inheritance" project, then you'll see > that the profile is being activated in the > "maven-invoker-profile-inheritance-dependency" project (and in result the > echo-maven-plugin will be executed) I couldn't find a way to prevent this > behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)