jaimecasero
commented
8 years ago <plugin>
<groupId>org.jibx</groupId>
<artifactId>jibx-maven-plugin</artifactId>
<version>1.2.6</version>
<executions>
<execution>
<id>JiBX Generate Sources</id>
<phase>generate-sources</phase>
<goals>
<goal>schema-codegen</goal>
</goals>
<configuration>
<customizations>
<customization>${basedir}/src/main/config/custom.xml</customization>
</customizations>
<targetDirectory>${basedir}/target/generated-sources</targetDirectory>
<includeSchemas>
<includeSchema>mlp_svc_result_310.xsd</includeSchema>
<includeSchema>mlp_svc_init_310.xsd</includeSchema>
</includeSchemas>
</configuration>
</execution>
<execution>
<id>JiBX Compile Bindings</id>
<phase>process-classes</phase>
<goals>
<goal>bind</goal>
</goals>
<configuration>
<schemaBindingDirectory>target/generated-sources</schemaBindingDirectory>
<load>true</load>
<validate>true</validate>
<!--<verbose>true</verbose>-->
<verify>true</verify>
</configuration>
</execution>
</executions>
</plugin>
angrygreenfrogs
deruelle
FerUy
Current solutions requires jixb jars to be included in code, and different profiles for linux/windows when setting paths.By using jixb plugin all of these would be unnecessary.
In addition, on systems with different java version the build may fail, since the exec maven plugin is not using the "java" goal, a java version for compiling may be using, while schema compiling uses system wide java version...