You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/04/09 16:20:34 UTC

[jira] Closed: (MNG-4120) Profile activation should be per module

     [ http://jira.codehaus.org/browse/MNG-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MNG-4120.
-----------------------------

      Assignee: Brett Porter
    Resolution: Duplicate

> Profile activation should be per module
> ---------------------------------------
>
>                 Key: MNG-4120
>                 URL: http://jira.codehaus.org/browse/MNG-4120
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies, POM
>    Affects Versions: 2.0.9
>            Reporter: Karsten Tinnefeld
>            Assignee: Brett Porter
>
> In a multi-module-project, one might wish to run certain targets dependent on the existance of some file or directory.
> In a single-module-project, I'd say
> <profiles><profile><id>do-if-file-exists</id>
> <activation><exists>some/special/path</exists></activation>
> <plugins><!-- my specific configuration --></plugins></profile></profiles>
> This however does not work on a per-module base in a multi-module project, but the profile is (de)activated depending on the situation on the run pom only, and this is not even documented.
> In my opinion, profile activation should be on a per-module basis.

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