[jboss-jira] [JBoss JIRA] (WFCORE-2805) Use Xalan from JRE rather than our own fork

[Peter Palaga (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408949#comment-13408949 ] 

Peter Palaga commented on WFCORE-2805:
--------------------------------------

I was able to do the following w.r.t. Xalan removal:

In WF Core:

* https://github.com/ppalaga/wildfly-core/tree/WFCORE-2805
* Xalan removed from pom.xml and module.xml files
* Xalan left as a dependency of xml-maven-plugin - it could perhaps be removed from there too, but some work needs to be done. 
* The transformer and serializer packages were added to both 
** OpenJDK https://github.com/ppalaga/wildfly-core/commit/501456f5fc524c3775360899dc8ce8cc4cb42d88#diff-7fe2ec262027ead4b4fbaf75cc251673R57
** and IBM JDK modules https://github.com/ppalaga/wildfly-core/commit/501456f5fc524c3775360899dc8ce8cc4cb42d88#diff-0e0f95e891ac20b3f5a2bf1151c29893R49
* Xalan added to banned deps in the config of enforcer plugin https://github.com/ppalaga/wildfly-core/commit/501456f5fc524c3775360899dc8ce8cc4cb42d88#diff-600376dffeb79835ede4a0b285078036R402
* -DallTests is passing on Oracle JDK
* -DallTests is passing on IBM with Elytron Subsystem tests excluded. Darran and Tomaž say Elytron Subsystem tests are known not to work on IBM JDK.

In WF:

* https://github.com/ppalaga/wildfly/tree/WFCORE-2805
* Added XsltClassLoadingTestCase to check as many in-XSLT class loading scenarios as possible: Loading a XSLT-processor built-in function, JRE Java method, custom method from the same module, custom method from a dependency module. https://github.com/ppalaga/wildfly/commit/e8c21f47cfec3f8629786f8a66fd74b1aabfb02e
* Xalan removed from pom.xml and module.xml files
* Xalan left as a dependency of xml-maven-plugin and maven-antrun-plugin - again, I see some potential to fix this
* Xalan added to banned deps in the config of enforcer plugin https://github.com/ppalaga/wildfly/commit/97fbec8ef360be80dbe6a4abfd76d8e7f74ea8ca#diff-600376dffeb79835ede4a0b285078036R536
* -DallTests is passing on Oracle JDK
* -DallTests is passing on IBM with some LDAP SSL tests excluded

[~dmlloyd] and [~ctomc] could you please to point me to some other specific scenarios that are not covered in [XsltClassLoadingTestCase|https://github.com/ppalaga/wildfly/commit/e8c21f47cfec3f8629786f8a66fd74b1aabfb02e] where the Xalan removal could fail?


> Use Xalan from JRE rather than our own fork
> -------------------------------------------
>
>                 Key: WFCORE-2805
>                 URL: https://issues.jboss.org/browse/WFCORE-2805
>             Project: WildFly Core
>          Issue Type: Task
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> As proposed by [~wolfc] we want to check if we can get rid of maintaining our own fork of Xalan.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)