You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/01/22 06:14:06 UTC
[jira] Created: (MNG-2000) Create comprehensive profiles
documentation
Create comprehensive profiles documentation
-------------------------------------------
Key: MNG-2000
URL: http://jira.codehaus.org/browse/MNG-2000
Project: Maven 2
Type: Task
Components: documentation - guides
Reporter: John Casey
Priority: Critical
Fix For: documentation
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-2000) Create comprehensive profiles
documentation
Posted by "Allan Ramirez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2000?page=all ]
Allan Ramirez reopened MNG-2000:
--------------------------------
Assign To: John Casey (was: Allan Ramirez)
For review/edits
> Create comprehensive profiles documentation
> -------------------------------------------
>
> Key: MNG-2000
> URL: http://jira.codehaus.org/browse/MNG-2000
> Project: Maven 2
> Type: Task
> Components: Documentation: Guides
> Reporter: John Casey
> Assignee: John Casey
> Priority: Critical
> Fix For: documentation
>
> Original Estimate: 16 hours
> Time Spent: 1 day
> Remaining: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-2000) Create comprehensive profiles
documentation
Posted by "Allan Ramirez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2000?page=all ]
Allan Ramirez updated MNG-2000:
-------------------------------
Remaining Estimate: 16 hours
Original Estimate: 16 hours
> Create comprehensive profiles documentation
> -------------------------------------------
>
> Key: MNG-2000
> URL: http://jira.codehaus.org/browse/MNG-2000
> Project: Maven 2
> Type: Task
> Components: Documentation: Guides
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
> Fix For: documentation
>
> Original Estimate: 16 hours
> Remaining: 16 hours
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-2000) Create comprehensive profiles
documentation
Posted by "Allan Ramirez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2000?page=all ]
Allan Ramirez closed MNG-2000:
------------------------------
Resolution: Fixed
Modified in svn
> Create comprehensive profiles documentation
> -------------------------------------------
>
> Key: MNG-2000
> URL: http://jira.codehaus.org/browse/MNG-2000
> Project: Maven 2
> Type: Task
> Components: Documentation: Guides
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
> Fix For: documentation
>
> Original Estimate: 16 hours
> Time Spent: 1 day
> Remaining: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-2000) Create comprehensive profiles
documentation
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2000?page=all ]
John Casey updated MNG-2000:
----------------------------
Fix Version: documentation
> Create comprehensive profiles documentation
> -------------------------------------------
>
> Key: MNG-2000
> URL: http://jira.codehaus.org/browse/MNG-2000
> Project: Maven 2
> Type: Task
> Components: documentation - guides
> Reporter: John Casey
> Priority: Critical
> Fix For: documentation
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org