[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622137#comment-17622137
]
ASF GitHub Bot commented on MNG-6609:
-------------------------------------
kwin commented on PR #835:
URL: https://github.com/apache/maven/pull/835#issuecomment-1286667062
Agreed, it is kind of a workaround, but given that I think it is consensus
to stick with POM 4.0 for Maven 4 this is the only near term solution I could
come up with.
> 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
>
> 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)
