[
http://jira.codehaus.org/browse/MNG-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190585#action_190585
]
Florian Poulin commented on MNG-3524:
-------------------------------------
In your case, the problem is that you use a parameter in your file path :
${project.build.directory}
So the bug is not on the <missing> tag (there is the same problem with
<exists>) but more on the fact that parameters are not admitted in the paths
(and should be, in my opinion, and according to the documentation).
> Profile to be activated when file is missing is always activated
> ----------------------------------------------------------------
>
> Key: MNG-3524
> URL: http://jira.codehaus.org/browse/MNG-3524
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.9
> Reporter: Adrian Hempel, Atlassian
> Fix For: 2.2.x
>
> Attachments: pom.xml
>
>
> When I run "mvn integration-test" with the attached pom.xml, the antrun:run
> goal is always executed, even when the ${project.build.directory}/built file
> is present.
> I would expect that the <missing> element would ensure that the profile
> containing the antrun:run goal would only be activated when that file is
> missing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
