| Key: |
MNG-2609
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Paul Gier
|
| Reporter: |
Gwyn Evans
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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.
|
|
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. |
Show » |
|
Mention 'activeByDefault' in the "Introduction to Build Profiles" guide
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...