[
https://issues.apache.org/jira/browse/MINVOKER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432703#comment-17432703
]
Karl Heinz Marbaise commented on MINVOKER-180:
----------------------------------------------
Please create a new issue instead of commenting on closed issues.
> Profiles are passed to invoked executions since version 1.6
> -----------------------------------------------------------
>
> Key: MINVOKER-180
> URL: https://issues.apache.org/jira/browse/MINVOKER-180
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.6, 1.7, 1.8, 1.9
> Environment: Maven 3.2.3
> Reporter: Frank Jakop
> Assignee: Karl Heinz Marbaise
> Priority: Blocker
> Attachments: maven-invoker-profile-inheritance.zip
>
>
> We recently upgraded to version > 1.5 (tried all versions) of invoker plugin
> and it seems to me that starting with 1.6 all profiles, which are activated
> on the invoker-triggering project are now passed into the invoked lifecycles.
> This is a blocker for us, because now too much mojo executions take place,
> which fail our builds.
> I attached a test case. To reproduce, unpack and go to
> maven-invoker-profile-inheritance. Run "mvn generate-resources -PmyProfile"
> and you see the echo mojo being executed and printing "########## Running in
> myProfile ##########".
> Now change the version of invoker plugin to 1.5 and repeat the test. You will
> notice that the mojo is not executed.
> According to the docs this is the expected behaviour, since we do not have
> invoker.profiles file and do set the profiles for the invocation explicitly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
