You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/11/16 18:53:00 UTC
[jira] [Commented] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634975#comment-17634975 ]
Hudson commented on MNG-6609:
-----------------------------
Build unstable in Jenkins: Maven » Maven TLP » maven » PR-833 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-833/2/
> 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-candidate, 4.0.0
>
>
> 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)