Bugzilla – Full Text Bug Listing
| Summary: | Regression : sources management | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Gael Lalire <gael.lalire> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | igor |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
*** This bug has been marked as a duplicate of bug 335711 *** |
Build Identifier: 20110602-0820 I add lifecycleMappingMetadata to avoid org.codehaus.mojo:jaxb2-maven-plugin:1.3 plugin error (future famous "plugin execution not covered") with an execute action. The sources are effectively generated (execute is recognized), however the execute action have to check the maven path (ie ${project.compileSourceRoots}) to automatically add target/generated-sources/jaxb to eclipse build path. If you simply check the maven path after executing you also not need to create some plugin to manage build-helper-plugin for example. Reproducible: Always Steps to Reproduce: 1. Create a project with a plugin adding a source path (build-helper, axis, jaxb, ...) 2. Tell m2e to execute the plugin 3. See that eclipse build path is not modified