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

Hudson commented on XMLSCHEMA-53:
---------------------------------

SUCCESS: Integrated in Jenkins build xmlschema-trunk #251 (See 
[https://builds.apache.org/job/xmlschema-trunk/251/])
XMLSCHEMA-53: Drop support for DOM 2. (veithen: rev 1837502)
* (edit) 
xmlschema-core/src/main/java/org/apache/ws/commons/schema/SchemaBuilder.java
* (edit) 
xmlschema-core/src/main/java/org/apache/ws/commons/schema/XmlSchemaCollection.java
* (edit) 
xmlschema-core/src/main/java/org/apache/ws/commons/schema/utils/DOMUtil.java


> Illegal reflective access by org.apache.ws.commons.schema.utils.DOMUtil 
> ------------------------------------------------------------------------
>
>                 Key: XMLSCHEMA-53
>                 URL: https://issues.apache.org/jira/browse/XMLSCHEMA-53
>             Project: XmlSchema
>          Issue Type: Bug
>            Reporter: Matthew Chegash
>            Priority: Major
>
> When using java 10, the following compile-time warning occurs:
> WARNING: An illegal reflective access operation has occurred
>  WARNING: Illegal reflective access by 
> org.apache.ws.commons.schema.utils.DOMUtil 
> ([file:/workforce/builds/current_integration/workforce/web/WEB-INF/lib/XmlSchema-1.4.7.jar|file:///workforce/builds/current_integration/workforce/web/WEB-INF/lib/XmlSchema-1.4.7.jar])
>  to method 
> com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.getXmlEncoding()
>  WARNING: Please consider reporting this to the maintainers of 
> org.apache.ws.commons.schema.utils.DOMUtil
>  WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
>  WARNING: All illegal access operations will be denied in a future release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to