[jira] [Closed] (MINVOKER-180) Profiles are passed to invoked executions since version 1.6

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MINVOKER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MINVOKER-180.
----------------------------------------
    Resolution: Not A Problem
      Assignee: Karl Heinz Marbaise

May be I misunderstand a thing here but if you explicitly define a profile in the invocation of maven-invoker-plugin it will of course given to the invoked projects as the documentations stated. If you don't like to have that you should use the {{invoker.profiles}} where you can define a profile for each project separately.  So I will close the issue. If you have further informations please don't hesitate to reopen the issue...

> 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
(v6.3.4#6332)