Maven 2 & 3

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)

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Dependencies, Profiles
  • Labels:
    None
  • Complexity:
    Expert
  • Number of attachments :
    0

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.

Activity

Hide
Brett Porter added a comment -

profiles.xml was removed from maven 3.x

Show
Brett Porter added a comment - profiles.xml was removed from maven 3.x

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: