[MNG-331] design profile and filtering solution

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-alpha-3
• Assignee: John Dennis Casey
• Reporter: Brett Porter
• Created: 19/Apr/05 23:27
• Updated: 01/Feb/06 14:42
• Resolved: 08/Jun/05 01:39

Description

as discussed on the ML, need to be able to build different types of artifacts for development by switching profiles (this can also be used to switch deployment environments).

The final environment - QA or even earlier - should not be filtered differently to production, but instead we swhould sort out a way to reprocess the artifacts more predictably and suggest a best practice of externalising all configuration so the artifact doesn't change at all.

Issue Links

• is related to: MNG-295 ./build.properties equivalent
• is related to: MNG-421 process profiles before repositories are used
• is related to: MNG-178 filter definition
• is related to: MNG-210 allow different profiles/environments for repositories
• is related to: MNG-354 Add ability to select modules to build based on a configuration