Maven 2 & 3

Plugins need to offer up all information without executing

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

In an IDE environment, you want to know what will be generated by a plugin without having it execute. For example, if you have a plugin that generates a source directory you want to know that without having actually execute the plugin because it can take a long time if you have a lot of plugins.

Another issue will probably have to be created to outline changes to the plugin api so that external tools can call this method to get all the information up-front. I couldn't find any related issues.

This should also work when reactor projects are run.

Another example is any plugin that produces resources that need to be added to the UI.

Issue Links

depends upon

New Feature - A new feature of the product, which has yet to be developed. MNG-193 symmetry for outputs of a plugin

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MEVENIDE-595 java package for generated sources trunkated

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Bug - A problem which impairs or prevents the functions of the product. MNGECLIPSE-79 Plugin does not execute generate-test-sources and generate-test-resources goals

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNGECLIPSE-163 Plugin doesn't add extra sources directories which are added using the build-helper-maven-plugin

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-1450 no easy way to figure generated source roots for a project

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
supercedes

Bug - A problem which impairs or prevents the functions of the product. MNG-1450 no easy way to figure generated source roots for a project

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Trygve Laugstøl added a comment -

This sounds like a Maven Extension Proposal (MEP) to me!

Show
Trygve Laugstøl added a comment - This sounds like a Maven Extension Proposal (MEP) to me!
Hide
Permalink
Eugene Kuleshov added a comment -

Jason, in a mean time (for short term) it would be enough to get back all the resources and source generated by plugins during Maven execution cycle. So, I can call generate-sources and capture source folders registered by plugins. See sample project mngeclipse-75-xmlbeans-testcase.zip in http://jira.codehaus.org/browse/MNGECLIPSE-75

Show
Eugene Kuleshov added a comment - Jason, in a mean time (for short term) it would be enough to get back all the resources and source generated by plugins during Maven execution cycle. So, I can call generate-sources and capture source folders registered by plugins. See sample project mngeclipse-75-xmlbeans-testcase.zip in http://jira.codehaus.org/browse/MNGECLIPSE-75
Hide
Permalink
Eugene Kuleshov added a comment -

This is probably the same as MNG-1450

Show
Eugene Kuleshov added a comment - This is probably the same as MNG-1450
Hide
Permalink
Brett Porter added a comment -

this seems like the more general case of MNG-1450, I'll close it as superceded

Show
Brett Porter added a comment - this seems like the more general case of MNG-1450 , I'll close it as superceded
Hide
Permalink
Jason van Zyl added a comment -

So this really includes all the outputs of a plugin plus any other behaviour that we might want to know about. Right now now I can only think of outputs and information that already exists in the generated plugin.xml.

Show
Jason van Zyl added a comment - So this really includes all the outputs of a plugin plus any other behaviour that we might want to know about. Right now now I can only think of outputs and information that already exists in the generated plugin.xml.
Hide
Permalink
Milos Kleint added a comment -

here's my idea that I would like to prototype.
1. add a method to the DefaultLifeCycleExecutor class that would return the lifecycle map (correctly ordered i guess)
2. that would contain all the plugin mappings to the liecycle phases
3. and have the parameters resolved correctly, both the ones defined in pom and the default ones.. all the param value should be just dom trees, no beans to prevent classloading issues

that way one could query into what the project setup is without running it. Ideally one would have the export parameters marked (eg. the source roots location for generated sources) in the plugin description, but one could probably get away with a plugin+parameter mapings on the IDE side for the start. There are not so many plugins that generate sources.

Show
Milos Kleint added a comment - here's my idea that I would like to prototype. 1. add a method to the DefaultLifeCycleExecutor class that would return the lifecycle map (correctly ordered i guess) 2. that would contain all the plugin mappings to the liecycle phases 3. and have the parameters resolved correctly, both the ones defined in pom and the default ones.. all the param value should be just dom trees, no beans to prevent classloading issues that way one could query into what the project setup is without running it. Ideally one would have the export parameters marked (eg. the source roots location for generated sources) in the plugin description, but one could probably get away with a plugin+parameter mapings on the IDE side for the start. There are not so many plugins that generate sources.

People

  • Assignee:
    Jason van Zyl
    Reporter:
    Jason van Zyl
Vote (3)
Watch (5)

Dates

  • Created:
    Updated: