You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2022/11/28 08:10:00 UTC

[jira] [Reopened] (MNG-6609) Profile activation by packaging

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

Tamas Cservenak reopened MNG-6609:
----------------------------------

Reverted breaking change on maven-3.9.x  [https://github.com/apache/maven/commit/36ff9a65e637cc9054c0ed04814305a0493b701b]

 

IT should be added:

https://github.com/apache/maven/pull/849#issuecomment-1328673965

> Profile activation by packaging 
> --------------------------------
>
>                 Key: MNG-6609
>                 URL: https://issues.apache.org/jira/browse/MNG-6609
>             Project: Maven
>          Issue Type: Improvement
>          Components: Profiles
>    Affects Versions: 3.6.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3
>
>
> Due to the lack of mixins, it is common that modules which use different packagings share the same parent pom. As those often use different dependencies/plugins, it would be nice to have profiles which are activated based on the packaging of a module. That is currently not possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)