[
http://jira.codehaus.org/browse/MNG-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-1879.
-----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.x (to be reviewed))
profiles.xml was removed from maven 3.x
> Allow dependencies to be defined in external profiles.xml for inclusion at
> build time when a profile is activated (and allow reuse of profies.xml)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-1879
> URL: http://jira.codehaus.org/browse/MNG-1879
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, Profiles
> Reporter: Rahul Thakur
>
> Here's a use-case where I believe it would make sense to allow <dependencies>
> to be defined for profiles in profiles.xml.
> Lets says I have a web-project that sets up profiles.xml for target build
> environments that it can be deployed on. Target environments can each have
> different J2EE containers. Now this is what happens when I setup my project
> for builds/deploys.
> 1) Set up a build control project, a minimal pom.xml that has contains SCM
> connection to my web-project above.
> 2) checks out profiles.xml first so now the build control project has a
> minimal pom + profiles.xml.
> 3) checks out the web-project under ${basedir}/target
> 4) I can activate a particular profile, based on which some operations can be
> done by a custom Plugin before an embedded instance of maven is spawned
> and some goals (specific to that profile) are delegated down to the checked
> out project.
--
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
