[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808895#comment-16808895
]
Robert Scholte commented on MNG-6609:
-------------------------------------
The issue is known, but in general profiles is never the solution. In general I
consider profiles evil as they are too strong and too often used for the wrong
reasons. It would also require a change to the pom 4.0.0 model, which is not
that simple.
What's missing is a more finegrained inheritence strategy. Right now a
[Plugin|https://maven.apache.org/ref/3.6.0/maven-model/maven.html#class_plugin]
has the {{inherited}} option, which is simply true or false. However, it is a
String, which opens possibilities within the current pom version. You could
think of {{<inherited>jar</inherited>}} to define that this plugin
configuration should only apply to jar-modules.
IIRC there's a paragraph about it on
https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0
> 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
(v7.6.3#76005)
