It would be helpful if maven2 jobs would support maven 2 profiles
(http://maven.apache.org/guides/introduction/introduction-to-profiles.html).

We use them to group relevant modules for specific deployments.
I could see this working in a couple of different ways.
1) When creating a maven2 job, specify the profile, and only relevant sections
of the pom are parsed.

2) Allow for normal full pom parsing, but allow the user to choose/type the
desired profile. (Similar to how goals are entered). In this scenario perhaps
the set of downstream projects would need to be derived from the profile.