[
https://issues.apache.org/jira/browse/MNG-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383125#comment-15383125
]
ASF GitHub Bot commented on MNG-5910:
-------------------------------------
GitHub user rajivpjs opened a pull request:
https://github.com/apache/maven/pull/88
[MNG-5910] Fixed the description of the POM reference & added an exce…
Please review and let me know any changes.
Thanks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajivpjs/maven MNG-5910
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven/pull/88.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #88
----
commit a9e771408200d55e3a8943b26baaa9d8cd5ab23d
Author: Rajiv Jain <[email protected]>
Date: 2016-07-18T21:36:35Z
[MNG-5910] Fixed the description of the POM reference & added an exception
during build time for empty and missing properties
----
> Using both {{exists}} and {{missing}} in the same {{file}} element should
> lead to an exception
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-5910
> URL: https://issues.apache.org/jira/browse/MNG-5910
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.3
> Reporter: Konrad Windszus
>
> Currently it is not clear from the POM reference
> (https://maven.apache.org/pom.html#Activation), that the elements {{exists}}
> and {{missing}} below {{file}} are mutually exclusive, because only
> {{exists}} is considered if it is there (see also
> https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/FileProfileActivator.java#L91).
> Please make it clearer in the POM reference that not both of them should be
> used at the same time and also throw an exception during build time if that
> is the case (in the effective POM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)