[
https://issues.apache.org/jira/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375449#comment-16375449
]
Robert Scholte commented on MNG-3328:
-------------------------------------
The pom that ends up in the repository must be model 4.0.0 so any version of
Maven and other tools will understand it. These kind of changes might be
introduced in a next model definition, but only if it can be port back for
runtime consumption. For example, if a profile contains this kind of activation
AND contains a dependency, it cannot be ported back to model 4.0.0. Several
combinations must be verified first, not all are valid.
As long as the pom on the system is also the pom being deployed, this issue
cannot be solved.
> Allow multiple profile activation properties.
> ---------------------------------------------
>
> Key: MNG-3328
> URL: https://issues.apache.org/jira/browse/MNG-3328
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
> Affects Versions: 2.0.8
> Reporter: Paul Gier
> Priority: Major
> Fix For: 3.x / Backlog
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
> {code:xml}
> <activation>
> <properties>
> <my-prop-1>some-value</my-prop-1>
> <my-prop-2>another-value</my-prop-2>
> </properties>
> </activation>
> {code}
> This would provide more flexibility in profile activation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
