You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/10/24 11:21:00 UTC
[jira] [Resolved] (MNG-6609) Profile activation by packaging
[ https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved MNG-6609.
----------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Fixed in https://github.com/apache/maven/commit/79b6dd0babcb9865d20d32686ea2f65961f4718e and https://github.com/apache/maven-integration-testing/commit/1358d69b9aad2098ea0705cff74e0ac53e2f90d5 (IT)
> 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: 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)