warning printed when a pom does not use an activated profile is poorly worded
and also should not be printed for multi-module builds
------------------------------------------------------------------------------------------------------------------------------------
Key: MNG-4583
URL: http://jira.codehaus.org/browse/MNG-4583
Project: Maven 2 & 3
Issue Type: Bug
Components: Profiles
Affects Versions: 3.0-alpha-6, 2.2.1, 2.0.11
Reporter: Ian Springer
Priority: Minor
This is a followup to http://jira.codehaus.org/browse/MNG-3641. Refer to that
issue for the background.
The current warning message is:
"Profile with id: '" + explicitProfileId + "' has not been activated."
I think this message is misleading, because the profile actually is activated -
it's just not used at all in the pom being processed. I suggest changing the
message to something like:
"Profile with id '" + explicitProfileId + "' is activated, but this pom does
not contain any usages of the profile."
Also, I don't think it makes sense to print this warning at all in a
multi-module build. In the large multi-module project I work on, we have a
number of profiles that are only used in a handful of the 50 or so modules.
--
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
