Proposed Documentation Outline

POM

• Basics for identity
• Parent requirements

Existing Documents

• The Project Object Model (POM)

Inheritance

• Combinatorial approaches
• Application parent
• Organizational parent

Standard inheritance principles

• Local specification wins
• Exceptions to standard inheritance (artifactId, modelVersion, name, packaging, ...? not inherited)

Dependencies

• Scopes
• Optional flag
• Exclusions
• Dependency management
• Version ranges
• Conflict resolution

Plugins

• Minimal searchable identity part
• <pluginGroups> usage

Executions

• Phase binding
• Execution-level configuration
• Inheritance considerations

Lifecycle

• Sources of mojo bindings
  • Packaging
  • Forked lifecycle overlay
  • POM configuration
  • Active profiles
  • Super POM
• Forking considerations
  • Tracing entry point to avoid cycles
  • Handling cloned projects

Reactor

• Sorting
• Cyclic dependency checking
• Failure advice
  • Skipping dependents of failed builds
• Using fresh interdependency artifacts

Settings

• Proxy information
• Authentication information
• Mirrors
• Plugin groups
• Offline mode flag

Profiles

• Profile injection and inheritance
• What you can specify where - restrictions
• Activating
  • activeProfiles - where used
  • Activation section and activators
  • -P command-line switch
  • activeByDefault
• Warnings
• Effects on portability
• Violating 1:1 POM:artifact mapping (not sure what this is now...old notes...)

Repositories

• Aggregation patterns
  • Through inheritance
  • Through transitive resolution
  • Through activated profiles
• Blacklisting
• Using layouts
  • Using custom layouts
• Metadata controls
• Releases flag
• Snapshots flag and update interval
• Available transports

Reporting

• Providing configuration to reports
• Default reports and effects of overriding