Issue Details (XML | Word | Printable)

Key: MNG-860
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jason van Zyl
Votes: 4
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
Maven 2

Allow Mojos that don't participate in the lifecycle to be configured using profiles

Created: 09/Sep/05 09:35 AM   Updated: 29/Oct/07 06:57 PM
Component/s: Inheritance and Interpolation
Affects Version/s: None
Fix Version/s: 3.0

Time Tracking:
Original Estimate: 6 hours
Original Estimate - 6 hours
Remaining Estimate: 6 hours
Remaining Estimate - 6 hours
Time Spent: Not Specified
Remaining Estimate - 6 hours

Issue Links:
Duplicate
 

Complexity: Expert


 Description  « Hide
The particular use case here is setting the ${jdkName} variable to be used by the IDEA plugin are part of the generation of the IDEA project files. It would be nice to have this set across the board so that I don't have to specify it on the command line or in each POM (which would be very unwieldly). Chatting with John, it seems it would be reasonable only for Mojos that don't participate in the lifecycle as to ensure portability of the build. Mojos that are typically related to tooling are mojos that don't participate in the lifecycle like the IDE related plugins which are generally gear for a user specific setup. Here's an example of what might be nice to have in a settings.xml:

<profiles>
<profile>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-idea-plugin</artifactId>
<configuration>
<jdkName>/home/jvanzyl/jdk/1.5</jdkName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
<profiles>



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Brett Porter added a comment - 18/Sep/05 10:35 PM
should this be in profiles or only in settings? I agree these should only be applied to the command line introduced goals only.

John Casey added a comment - 28/Sep/05 11:28 AM
it may be useful to create a more stark distinction between direct-invocation mojos (which are closer to tools), and lifecycle mojos (which are phase bindings, or build-process steps)...then, the configuration of tools could go in the settings.xml file.

At any rate, we're getting into design issues here, and that's going to have to wait for 2.1, I think.


Dan Tran added a comment - 28/Sep/05 11:38 AM
Sound like http://jira.codehaus.org/browse/MNG-786 falls into the same category. But please have it fixed in
2.0

Without this feature, i can not do a good clean in one shot using reactor.