Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Documentation: Guides
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
It appears to be that the primary use-case for someone considering profiles would be the requirement to modify an existing build in some way to accomodate a 'special-case'. As such, it seems to me that a mention of the activation option 'activeByDefault' should be added.
At present, the document implies that there either needs to be a change in the command line (e,g, "-Denv-prod") or some form of environment parsing to have the build run as before, whereas 'activeByDefault' show that's not so but is not mentioned.
Also, the current description of 'activeByDefault' in the POM reference (http://maven.apache.org/ref/current/maven-model/maven.html) is sort of misleading, I find. At least, it doesn't add any value beside what the tag name itself offers: "Flag specifying whether this profile is active by default."
Diving a bit deeper (i.e., reading the discussions in related bug reports, such as
MNG-835andMNG-2136) it becomes clear that the semantics of 'activeByDefault' are not entirely trivial. The tag makes sense to have, and it's useful, but unfortunately it remains largely undocumented...MNG-835andMNG-2136) it becomes clear that the semantics of 'activeByDefault' are not entirely trivial. The tag makes sense to have, and it's useful, but unfortunately it remains largely undocumented...