[ http://jira.codehaus.org/browse/MNG-331?page=comments#action_40379 ] Brett Porter commented on MNG-331: ----------------------------------
a couple of thoughts: - instead of so much duplication in maven.mdo, can profile extend a common base with Model? - I think the original document specified profiles.xml to be the same as in pom.xml, but I can see why it should match settings.xml. Can you update the confluence doc according to your changes? > design profile and filtering solution > ------------------------------------- > > Key: MNG-331 > URL: http://jira.codehaus.org/browse/MNG-331 > Project: Maven 2 > Type: New Feature > Reporter: Brett Porter > Assignee: John Casey > Fix For: 2.0-alpha-3 > > > 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. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
