maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MNG-4120) Profile activation should be per module
Date Thu, 02 Apr 2009 20:53:12 GMT


Benjamin Bentmann commented on MNG-4120:

Looks like a dup of MNG-2363, isn't it? File-based profile activation resolves relative paths
against the current working directory, not the module base directory.

> Profile activation should be per module
> ---------------------------------------
>                 Key: MNG-4120
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies, POM
>    Affects Versions: 2.0.9
>            Reporter: Karsten Tinnefeld
> 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:
For more information on JIRA, see:


View raw message