blipsman
2014-03-13 22:29:14 UTC
I found solution:
To eliminate problem, which was to enforce using JAXB 2.1 ( which is
included in JAVA 6) , but not JAXB 2.2 I have added
to the parent POM:
*<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>1.5</version>
</plugin>
</plugins>
</pluginManagement>*
fixed the error in POM.xml
Still had to use *<target>2.1</target>* to make sure the 2.1 JAXB is used
instead of JAXB 2.2
Boris
--
View this message in context: http://maven.40175.n5.nabble.com/An-API-incompatibility-was-encountered-while-executing-org-codehaus-mojo-jaxb2-maven-plugin-1-6-xjc--tp5788280p5788281.html
Sent from the Maven - Users mailing list archive at Nabble.com.
To eliminate problem, which was to enforce using JAXB 2.1 ( which is
included in JAVA 6) , but not JAXB 2.2 I have added
to the parent POM:
*<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>1.5</version>
</plugin>
</plugins>
</pluginManagement>*
fixed the error in POM.xml
Still had to use *<target>2.1</target>* to make sure the 2.1 JAXB is used
instead of JAXB 2.2
Boris
--
View this message in context: http://maven.40175.n5.nabble.com/An-API-incompatibility-was-encountered-while-executing-org-codehaus-mojo-jaxb2-maven-plugin-1-6-xjc--tp5788280p5788281.html
Sent from the Maven - Users mailing list archive at Nabble.com.