maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karsten Tinnefeld (JIRA)" <>
Subject [jira] Issue Comment Edited: (MNG-4120) Profile activation should be per module
Date Wed, 01 Apr 2009 10:01:12 GMT


Karsten Tinnefeld edited comment on MNG-4120 at 4/1/09 5:00 AM:

In order to deliver configuration files etc. with the other project artifacts, I had this
defined in a profile attached to my master configuration pom in a large-scale banking portal
project. The idea is that this automatically copies the project attachments to the target
directory whenever src/main/attachments exists.

									<copy preservelastmodified="true" todir="${}"
										<fileset dir="${basedir}/src/main/attachments"
											includes="**/*" />
										<regexpmapper from="^(.*)$$"
											to="${project.artifactId}-${project.version}-\1" />

I would then attach these artifacts (did not yet figure out a generic way for it) in the concrete
projects, e.g. a log4j configuration:


Hope, this helps.

      was (Author: tinne):
    Second try.
> 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