You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gwyn Evans (JIRA)" <ji...@codehaus.org> on 2006/10/13 11:27:52 UTC

[jira] Created: (MNG-2609) Mention 'activeByDefault' in the "Introduction to Build Profiles" guide

Mention 'activeByDefault' in the "Introduction to Build Profiles" guide
-----------------------------------------------------------------------

                 Key: MNG-2609
                 URL: http://jira.codehaus.org/browse/MNG-2609
             Project: Maven 2
          Issue Type: Improvement
          Components: Documentation: Guides
            Reporter: Gwyn Evans


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.

-- 
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

        

[jira] Commented: (MNG-2609) Mention 'activeByDefault' in the "Introduction to Build Profiles" guide

Posted by "Olav Reinert (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96394 ] 

Olav Reinert commented on MNG-2609:
-----------------------------------

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-835 and MNG-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...


> Mention 'activeByDefault' in the "Introduction to Build Profiles" guide
> -----------------------------------------------------------------------
>
>                 Key: MNG-2609
>                 URL: http://jira.codehaus.org/browse/MNG-2609
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Documentation: Guides
>            Reporter: Gwyn Evans
>
> 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.

-- 
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

        

[jira] Closed: (MNG-2609) Mention 'activeByDefault' in the "Introduction to Build Profiles" guide

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MNG-2609.
--------------------------

    Resolution: Fixed

Added some notes about activeByDefault to the site, and added a better description of activeByDefault to the model.

> Mention 'activeByDefault' in the "Introduction to Build Profiles" guide
> -----------------------------------------------------------------------
>
>                 Key: MNG-2609
>                 URL: http://jira.codehaus.org/browse/MNG-2609
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Documentation: Guides
>            Reporter: Gwyn Evans
>            Assignee: Paul Gier
>             Fix For: 2.0.10, Documentation Deficit
>
>
> 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.

-- 
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

        

[jira] Updated: (MNG-2609) Mention 'activeByDefault' in the "Introduction to Build Profiles" guide

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MNG-2609:
---------------------------

    Fix Version/s: 2.0.10

> Mention 'activeByDefault' in the "Introduction to Build Profiles" guide
> -----------------------------------------------------------------------
>
>                 Key: MNG-2609
>                 URL: http://jira.codehaus.org/browse/MNG-2609
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Documentation: Guides
>            Reporter: Gwyn Evans
>            Assignee: Paul Gier
>             Fix For: 2.0.10, Documentation Deficit
>
>
> 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.

-- 
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