Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.6.0
-
None
Description
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.
Attachments
Issue Links
- causes
-
MNG-7606 Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
- Closed
- duplicates
-
MNG-4154 Profile activation based on module packaging type (e.g. jar, war, ear)
- Closed
- is related to
-
MNGSITE-502 Document activation based on packaging
- Closed
- relates to
-
MPOM-120 attach site descriptor only for pom packaging
- Closed
- links to