[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640186#comment-17640186
]
ASF GitHub Bot commented on MNG-6609:
-------------------------------------
cstamas commented on PR #883:
URL: https://github.com/apache/maven/pull/883#issuecomment-1329563048
Jut wanted to quickly "publish" my findings about the cause, but around same
time moved to something else :smile: feel free to reuse (no need to keep my
user ID, after all this is your change set with my one line removal). Or, I can
pick it up later.
> 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)
