[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17619760#comment-17619760
]
Casper Roubos commented on MNG-6609:
------------------------------------
I would hereby ask for your attention for this improvement (or perhaps bug,
since it's normal project property):
I would like to have this working as profile activation:
{code:java}
<profiles>
<profile>
<id>eclipse-test-pluginProfile</id>
<activation>
<property>
<name>project.packaging</name>
<value>eclipse-test-plugin</value>
</property>
</activation>
<properties>
...
{code}
Thanks in advance for your effort and time. This would be a big improvement in
simplifying our parent poms.
> 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
> 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)
