You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/27 13:46:23 UTC
[jira] Closed: (MNG-3524) Profile to be activated when file is
missing is always activated
[ http://jira.codehaus.org/browse/MNG-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3524.
----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.0-alpha-8)
Assignee: Benjamin Bentmann
Please note that properties referring to the POM, i.e. {{${project.*}}} cannot be used during profile activation, but both relative paths as well as the property {{${basedir}}} are now properly supported.
> 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 & 3
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.9
> Reporter: Adrian Hempel, Atlassian
> Assignee: Benjamin Bentmann
> 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