You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jan Steuerwald (JIRA)" <ji...@apache.org> on 2015/11/02 13:28:27 UTC
[jira] [Updated] (CXF-6659) CXF 2.7.17 defaults to JAXB 2.1 in Java
8
[ https://issues.apache.org/jira/browse/CXF-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Steuerwald updated CXF-6659:
--------------------------------
Description:
When using CXF 2.7.17 in a maven project with the JDK property set to "1.8", CXF uses the default dependency for JAXB (which is version 2.1), beacuse there is no profile for JDK 1.8 in the CXF parent pom.xml.
The correct dependency would be JAXB 2.2, so this leads to runtime exceptions.
The workaround is to exclude the transitive JAXB dependency in your own pom.xml and explicitly depend on JAXB with the right version.
In CXF 3 the problem is fixed, but the same problem will appear again with JDK 1.9
was:
When using CXF 2.7.17 in a maven project with the JDK property set to "1.8", CXF uses the default dependency for JAXB (which is version 2.1), beacuse there is no profile for JDK 1.8 in the CXF parent pom.xml.
The correct dependency would be JAXB 2.2, so this leads to runtime exceptions.
In CXF 3 the problem is fixed, but the same problem will appear again with JDK 1.9
> CXF 2.7.17 defaults to JAXB 2.1 in Java 8
> -----------------------------------------
>
> Key: CXF-6659
> URL: https://issues.apache.org/jira/browse/CXF-6659
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.7.17
> Environment: JDK 1.8
> Reporter: Jan Steuerwald
>
> When using CXF 2.7.17 in a maven project with the JDK property set to "1.8", CXF uses the default dependency for JAXB (which is version 2.1), beacuse there is no profile for JDK 1.8 in the CXF parent pom.xml.
> The correct dependency would be JAXB 2.2, so this leads to runtime exceptions.
> The workaround is to exclude the transitive JAXB dependency in your own pom.xml and explicitly depend on JAXB with the right version.
> In CXF 3 the problem is fixed, but the same problem will appear again with JDK 1.9
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)