Include support for executing plugins attached to the generated-sources lifecycle phase

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Project Configuration
  • Labels:
    None

Description

I have a jaxb2 plugin that I have configured, and which attaches itself to the generated-sources plugin. However, while m2eclise does add the /target/generated-classes/xjc folder to the source paths, it doesn't execute the source generation via the incremental compiler before re-compiling, so I end up having to execute "mvn generate-sources" manually from the command-line, then refresh.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNGECLIPSE-616 better out of the box experience

  • 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. 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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eugene Kuleshov added a comment -

I think we already have duplicated issue for this somewhere, In a mean time you can try the following options:

  • use run Maven / Update Source Folders from Eclipse if you need to regenerate your classes (assuming that goal to run on project update is set to "generate-sources" in global Maven configuration).
  • try to add your plugin goal to the list of goals executed for resource filtering in Maven settings for the given project.
  • add Maven builder to the project that would run your plugin on resource change

The last two options are available in project preferences dialog (respectively Maven and Builders)

Show
Eugene Kuleshov added a comment - I think we already have duplicated issue for this somewhere, In a mean time you can try the following options:
  • use run Maven / Update Source Folders from Eclipse if you need to regenerate your classes (assuming that goal to run on project update is set to "generate-sources" in global Maven configuration).
  • try to add your plugin goal to the list of goals executed for resource filtering in Maven settings for the given project.
  • add Maven builder to the project that would run your plugin on resource change
The last two options are available in project preferences dialog (respectively Maven and Builders)
Hide
Permalink
Joshua Pollak added a comment -

Related to this closed bug. I have the same issue with the jaxb1 plugin. I also have a test project I can upload that demonstrates the problem.

Show
Joshua Pollak added a comment - Related to this closed bug. I have the same issue with the jaxb1 plugin. I also have a test project I can upload that demonstrates the problem.
Hide
Permalink
Joshua Pollak added a comment -

This example project demonstrates adding generated-sources to the build path. M2Eclipse does not automatically add these as source directories.

Show
Joshua Pollak added a comment - This example project demonstrates adding generated-sources to the build path. M2Eclipse does not automatically add these as source directories.
Hide
Permalink
Luca added a comment -

I have same issue with the build-helper, the two added source folder are not recognized even if I specify the correct goal by import
I am not sure that Bug MNGECLIPSE-163 is really fixed

Show
Luca added a comment - I have same issue with the build-helper, the two added source folder are not recognized even if I specify the correct goal by import I am not sure that Bug MNGECLIPSE-163 is really fixed

People

  • Assignee:
    Unassigned
    Reporter:
    Christian Gruber
Vote (3)
Watch (2)

Dates

  • Created:
    Updated: