Maven 2 & 3

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

Details

  • Complexity:
    Expert
  • Number of attachments :
    0

Description

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>

Issue Links

Activity

Hide
Brett Porter added a comment -

should this be in profiles or only in settings? I agree these should only be applied to the command line introduced goals only.

Show
Brett Porter added a comment - should this be in profiles or only in settings? I agree these should only be applied to the command line introduced goals only.
Hide
John Casey added a comment -

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.

Show
John Casey added a comment - 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.
Hide
Dan Tran added a comment -

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.

Show
Dan Tran added a comment - 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.

People

Vote (4)
Watch (5)

Dates

  • Created:
    Updated:

Time Tracking

Estimated:
6h
Original Estimate - 6 hours
Remaining:
6h
Remaining Estimate - 6 hours
Logged:
Not Specified
Time Spent - Not Specified