[ 
https://issues.apache.org/jira/browse/XMLBEANS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861120#comment-17861120
 ] 

Reto Hoehener commented on XMLBEANS-651:
----------------------------------------

Thanks for that background info. I totally agree that undoing the change is the 
safer option.

As I understand, the JDK actually contains a repackaged version of Xerces.

The library we need to use (exificient) unfortunately really does depend on 
Xerces at compile- and runtime.

Sorry for the bother. Our pom hierarchies and resulting classpaths are a 
challenge to understand, and I was trying to make sense of all these various 
xml-api versions and exclusions I saw.

> xml-apis dependency clarification
> ---------------------------------
>
>                 Key: XMLBEANS-651
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-651
>             Project: XMLBeans
>          Issue Type: Wish
>            Reporter: Reto Hoehener
>            Assignee: PJ Fanning
>            Priority: Major
>             Fix For: Version 5.2.2
>
>
> Could you please explain the reason for the xml-apis dependency in the jdk 
> 1.8 profile? Are these classes not already part of Java 8?
> If there is no specific reason, can this dependency and profile be removed?
> POM v5.2.1: 
> https://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/5.2.1/xmlbeans-5.2.1.pom
> {code:java}
> <profiles>
>   <profile>
>     <id>java8</id>
>     <activation>
>       <jdk>1.8</jdk>
>     </activation>
>     <dependencies>
>       <dependency>
>         <groupId>xml-apis</groupId>
>         <artifactId>xml-apis</artifactId>
>         <version>1.4.01</version>
>       </dependency>
>     </dependencies>
>   </profile>
> </profiles>{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Reply via email to