maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karsten Tinnefeld (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2363) <profile><activation><file><exists/> does not work in a multi-project build
Date Thu, 02 Apr 2009 21:19:13 GMT

    [ http://jira.codehaus.org/browse/MNG-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171849#action_171849
] 

Karsten Tinnefeld commented on MNG-2363:
----------------------------------------

I stubled on this, as well (see MNG-4120:).

The title is a bit short-sighted, as <activation><property> (and, of course, <activation><file><missing>)
could also be module-dependent:

<project><parent><artifactId>parent</artifactId></parent>
<artifactId>project-a</artifactId>
<properties><some-property>true</some-property></properties></project>

<project><parent><artifactId>parent</artifactId></parent>
<artifactId>project-b</artifactId>
<properties><some-property>false</some-property></properties></project>

should also be selectively running a target based on a profile

<project><artifactId>parent</artifactId>
<properties><activation><property><name>some-property</name><value>true</value></property></properties>
<build><!-- project-a specific actions here --></build></project>

> <profile><activation><file><exists/> does not work in a multi-project
build
> ---------------------------------------------------------------------------
>
>                 Key: MNG-2363
>                 URL: http://jira.codehaus.org/browse/MNG-2363
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Profiles
>            Reporter: David Boden
>            Priority: Critical
>             Fix For: 2.1.x
>
>         Attachments: problemactivation.zip, screenshot-1.jpg
>
>
> I would expect each subproject to have the profile turned on or off depending on whether
${basedir}/file-to-check-for exists.
> Instead, during a multi-project build the profile is either on or off depending on whether
the file exists relative to the *aggregator pom*. The decision is made once.
> Variable substitution doesn't work, so I can't explicitly use <exists>${basedir}/file-to-check-for</exists>
or any variation on this theme to workaround the bug.
> Some background to my particular problem. I have 10 modules to build. Some of them are
GUI modules and contain a file called plugin.xml in the subproject directory. I want to package
these up specially and sign them, ready for deployment to webstart. The other modules are
shared and server code and I don't want these packaged in the same way. So, I've got a dependency
in my *parent* pom file which activates a profile called "guibundle" if a plugin.xml file
exists in the subproject directory.

-- 
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

        

Mime
View raw message