Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Dependencies, Profiles
-
Labels:None
-
Complexity:Expert
-
Number of attachments :
Description
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.
profiles.xml was removed from maven 3.x