| Summary: | [mojo] org.jibx:maven-jibx-plugin:schema-codegen support | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Joerg Buchberger <lists> | ||||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||||
| Status: | CLOSED INVALID | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | don, igor | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=350809 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Joerg Buchberger
Created attachment 199887 [details]
import error screenshot
If you workaround the impor errors by "resolve-all-later" and then using "Quick Fix" + changing "action" from "ignore" to "execute" ... you will get the following addition to your pom:
<pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.jibx</groupId>
<artifactId>
maven-jibx-plugin
</artifactId>
<versionRange>[1.2.3,)</versionRange>
<goals>
<goal>bind</goal>
<goal>schema-codegen</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute/>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
Then you get the error message:
"Binding binding.xml is unusable because of validation errors (org.jibx:maven-jibx-plugin:1.2.3:bind:jibx-bind:process-classes)"
After "Maven Update Project Configuration" and a few cycles of "Refresh", "Eclipse-Clean", "Restart" and "Runs as mvn install" ... the validation error goes away ...
If you import the Maven project with the pom already prepared with above lifecycle-mapping ... you just get aforementioned binding error, which goes away after "mvn install" Note, however, that error comes back when doing "Eclipse Clean" - need to find out, how to execute as part of Eclipse clean and incremental builds as well. Why not write proper m2e support for maven-jibx-plugin as explained in [1]? [1] http://wiki.eclipse.org/M2E_Extension_Development closing old/stale bugreports |