neils-dev commented on pull request #2153:
URL: https://github.com/apache/ozone/pull/2153#issuecomment-819956555


   Thanks **@adoroszlai** for comments on classpath jars resulting from pom 
build file changes for _jaxb_ upgrade.  Yes, unintentionally included is the 
_org.glassfish jaxb-core_.  Apparently it is pulled in from the _org.glassfish 
jaxb-runtime_ upgrade.  Both _jaxb-core_ jars are unnecessary.  New commit 
removes the non _glassfish jaxb-core_ - thanks!  In addition also removed older 
_jaxb-impl_ dependency as it is the old jaxb runtime which is replaced with the 
new _org.glassfish jaxb-runtime_.  FYI : The following two jiras from another 
apache project follows what we are doing here: 
https://issues.apache.org/jira/browse/TIKA-2743,https://issues.apache.org/jira/browse/TIKA-2778.
  **NOTE**: we are also pulling in an additional jar that we have dependency 
on, the _javax.activation_ - currently in the base pom file we have the version 
1.1.1 dependency, however we have **_also_** the 1.2.0 version (I believe from 
the jaxb-runtime).  Tried updating the base pom.xml file to:         
   ```
   <dependency>
           <groupId>javax.activation</groupId>
           <artifactId>activation</artifactId>
           <version>1.2.0</version>
         </dependency>
   ```
   however this results in a recon build problem (see attached image).  
Therefore _**left**_ the _javax.activation_ version at current 1.1.1.
   
   ![recon_build_failure_activation_1 2 
0](https://user-images.githubusercontent.com/81126310/114801167-67421900-9d58-11eb-9a58-4399859d938e.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to