Issue #888 has been updated by Soisik Froger.
Hi Raphael, 1. I'm not downgrading maven-jaxb2-plugin, the idea is to keep the same version (I'm on the 2.1 branch), I'll upgrade in the 2.2 2. In 2.1, I need distinct profile for the quick fix property javadoc.opt. BTW, when we will upgrade libraries and fix the javadoc warning, we won't need these profiles anymore : bouncycastle now comes with a single artifact that works for jdk15 "and on" 3. I'm lazy :) so I'd rather not do the job twice, so my plan is to correct these errors in the 2.2 branch (there are over 100 errors) Hope I've answered your concerns. ---------------------------------------- Bug #888: Mvn build fails with Java 8 http://tools.lsc-project.org/issues/888 Author: Soisik Froger Status: New Priority: Normal Assigned to: Category: Packaging Target version: 2.1.4 Problem in version: 2.1.3 Environment : Apache Maven 3.3.9, JDK version: 1.8.0_111 Command : mvn -opendj clean package Here are some minor adaptations on the pom.xml so LSC can be built successfully with java 8 without having to switch to JDK 7 or 6. 1. bc-jdk-version property missing, Solution : simply adding a jdk18 profile based on jdk17 profile. 2. "'file' access is not allowed due to restriction set by the accessExternalSchema property" during maven-jaxb2-plugin generate-sources phase : org.xml.sax.SAXParseException; systemId: jar:file:/home/sfroger/.m2/repository/com/sun/xml/bind/jaxb-xjc/2.2.6/jaxb-xjc-2.2.6.jar!/com/sun/tools/xjc/reader/xmlschema/bindinfo/binding.xsd; lineNumber: 52; columnNumber: 88; schema_reference: Failed to read schema document 'xjc.xsd', because 'file' access is not allowed due to restriction set by the accessExternalSchema property. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) See https://java.net/jira/browse/MAVEN_JAXB2_PLUGIN-80. Solutions : - Quick fix : Use the workaround provided in bug report : works. => I'd suggest we go for this solution for 2.1.4 - Long term fix : Upgrade maven-jaxb2-plugin from 0.8.0 to 0.9.0+ : works but I'd like to further analyze for potential side effects, because generated lsc.episode and WS API are differents when generated with newer plugins; => I will create a specific issue for libraries upgrade (target release is 2.2.0) 3. Javadoc generation fails when HTLM do not validate. See http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete - Quick fix : These errors can be ignored by the plugin by adding a property to jdk18 profile et passing it to the plugin during java doc generation <javadoc.opts>-Xdoclint:none</javadoc.opts> => I'd suggest we go for this solution for 2.1.4 - Long term fix : Correct the errors and warnings in the javadoc commentaries throughout source code => I will create a specific issue for this task (targeted release is 2.2.0). Lots of classes will be impacted. See attached patch. Notes : - Also tested with Apache Maven 3.0.2 & Java 1.6. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
