[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808602#comment-16808602 ]
Konrad Windszus commented on MNG-6609: -------------------------------------- One example would be one common parent pom for modules of packaging "jar" and "content-package" (supported via http://jackrabbit.apache.org/filevault-package-maven-plugin/index.html). While it makes sense to e.g. configure certain (custom) maven-enforcer-rules for "jars", I certainly don't want those to be executed for "content-packages" (as in general content-packages are not supposed to contain e.g. java classes, therefore executing rules which refer to java classes won't make sense for "content-packages"). Therefore I would like to configure the maven-enforcer rule custom goal execution in a package-specific profile (which is only active for "jar"). > 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)