You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/01/09 18:34:22 UTC

[jira] Updated: (MNG-2000) Create comprehensive profiles documentation

     [ http://jira.codehaus.org/browse/MNG-2000?page=all ]

Jason van Zyl updated MNG-2000:
-------------------------------

    Fix Version/s:     (was: 2.0.5)
                   2.0.6

> Create comprehensive profiles documentation
> -------------------------------------------
>
>                 Key: MNG-2000
>                 URL: http://jira.codehaus.org/browse/MNG-2000
>             Project: Maven 2
>          Issue Type: Task
>          Components: Documentation: Guides
>            Reporter: John Casey
>         Assigned To: John Casey
>            Priority: Critical
>             Fix For: 2.0.6
>
>   Original Estimate: 16 hours
>          Time Spent: 1 day
>  Remaining Estimate: 0 minutes
>
> This document should draw from the mailing list, FAQ wiki, MNGFAQ jira project (on codehaus), existing site documentation, project source code, and any IRC conversations necessary.
> It should include:
> * How can I tell which profiles are in effect during a build?
> * What are the different types of profile? Where is each defined?
> * Which areas of a POM can be customized by each type of profile? Why?
>     - settings-defined and profiles.xml-defined only modify properties, repositories, and pluginRepositories. This is necessary to preserve the portability of the pom as much as possible, since these two locations are not installed/deployed to the repository system.
> * How can a profile be triggered? How does this vary according to the type of profile being used?
> * Profiles are not inherited, but their effects are, because they are applied to the POM before it's used for inheritance. This means a parent POM will have its profiles triggered and applied before it is used to calculate the inherited values for the current POM. Please include this in the documentation as well.
> There's probably more, but I can't think of it off the top of my head. We need to make this another one of those definitive documents for POM configuration.

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