[ http://jira.codehaus.org/browse/MNG-331?page=comments#action_40360 ]
John Casey commented on MNG-331:
--------------------------------
first pass at the profiles model work has been finished. settings.xml,
profiles.xml, and pom.xml are all valid points for specifying profiles, but
only the latter allows specification of non-repository, non-properties values.
settings.xml and profiles.xml only allow specification of context properties
(things for resolving expressions like ${tomcat.version}) and
repository/pluginRepository.
profiles in the pom.xml CANNOT specify context properties, since this is not
part of the POM specification itself (maybe this needs revision for profiles
only...).
Please note that profiles have not been wired into the inheritance, etc.
hierarchy, and are not currently an effective means of modifying the build.
> 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]
