[MNG-2000] Create comprehensive profiles documentation

• Type: Task
• Status: Closed
• Priority: Critical
• Resolution: Incomplete
• Component/s: Documentation: Guides
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 21/Jan/06 23:12
• Updated: 06/Apr/15 00:47
• Resolved: 23/Jan/14 18:48

Description

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.

Issue Links

• is depended upon by: MNGSITE-15 Create an archetype demonstrating the use of profiles targeting different environments
• is depended upon by: MNG-1307 Document profile injection in conjunction with inheritance
• relates to: MNG-2857 Intro to the POM implies profiles are inherited