jira-importer commented on issue #626: URL: https://github.com/apache/maven-invoker-plugin/issues/626#issuecomment-2957809152
**[Zbigniew Lis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=zbilis)** commented [Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise) I know this is years later, but the problem is still there, and I think the author was misunderstood. 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. You should be able to reproduce it using project provided by the author: 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. And this happens only in versions 1.6 and higher. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
