Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

m2e: plugin should be run on configuration #33

Closed
victornoel opened this issue Jan 5, 2015 · 2 comments
Closed

m2e: plugin should be run on configuration #33

victornoel opened this issue Jan 5, 2015 · 2 comments
Assignees
@highsource
Labels
bug
Milestone
0.13.0

Comments

@victornoel
Copy link

Hi,

Because the plugin adds a source directory, the lifecycle configuration should be run on configuration for m2e to pick-up the extra source folder.

The change would be trivial in lifecycle-mapping-metadata.xml

Note that it seems that the default plugin maven-jaxb2-plugin is ok, but the jaxb20, jaxb21 and jaxb22 are wrong.
@highsource
Copy link
Owner

Thank you for the report!

I'll make lifecycle-mapping-metadata.xml identical in all the four cases, as in the maven-jaxb2-plugin.

@highsource highsource added this to the 0.12.4 milestone Jan 5, 2015
@highsource highsource self-assigned this Jan 5, 2015
highsource added a commit that referenced this issue Jan 5, 2015
@highsource
Fixes issue #33.
546745b
@highsource
Copy link
Owner

Is fixed now, will be released in 0.12.4. Thank your the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@highsource highsource

Labels
bug
Projects
None yet
Milestone
0.13.0
Development

No branches or pull requests
2 participants
@victornoel @highsource