There is a Jira ticket for this problem, which I provided a patch for quite a while ago.

http://jira.codehaus.org/browse/MRELEASE-415

It'd be nice if the issue could get some attention by the developers.

Reinhard


Eugeny N Dzhurinsky schrieb:
Hello there!

I am facing some strange problem with the profile definition. Looks like if
there is the file profiles.xml, located in the same directory as the pom.xml
for the parent project - specifying one of the profiles with -P switch does
not affect child modules. At least

mvn help:active-profiles -Puser

does show the desired profile in the active profiles list, but it does not
show the desired profile as the active profile for submodules:

=====================================================================================
[INFO] Scanning for projects...
[INFO] Reactor build order: [INFO] profileIssue
[INFO]   module1
[INFO]   module2
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO] ------------------------------------------------------------------------
[INFO] Building profileIssue
[INFO]    task-segment: [help:active-profiles] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [help:active-profiles]
[INFO] Active Profiles for Project 'test:profileIssue:pom:1.0-SNAPSHOT':
The following profiles are active:

 - user (source: profiles.xml)



Active Profiles for Project 'test:module1:jar:1.0-SNAPSHOT':
There are no active profiles.



Active Profiles for Project 'test:module2:jar:1.0-SNAPSHOT':
There are no active profiles.



[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Tue Jun 16 11:47:33 EEST 2009
[INFO] Final Memory: 5M/11M
[INFO] ------------------------------------------------------------------------
=====================================================================================

the effective pom does not contain properties, defined in the profiles.xml,
for the sub-modules as well.

So looks like it is not possible to configure the set of shared properties to
be used by all modules in the multi-module project? Or may be there is some
another way of doing this?

Thank you in advance!



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to