[
https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518615#comment-16518615
]
Daniel Kulp commented on XERCESJ-1695:
--------------------------------------
You'll need to figure that out separately with just the jars from the xerces
distribution or something. However, for pushing to central the 2.12.0
"xercesImpl" artifact, I'm going to go with the non-xml-schema 1.1 version.
The main reason is that I have a bunch of failures using the 1.1 version.
Mainly, the schema for OSGi blueprint can be parsed and validated with the
non-1.1 version, but fails with the 1.1 version. (
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd ) I'd rather have a
version that includes the security fixes but doesn't (hopefully) break peoples
applications. If we need a "schema 1.1" version in central, I would likely
push it as a separate artifact at this point.
That said, I'm still doing some testing.
> Xerces2J v 2.12 not available on Maven Central
> ----------------------------------------------
>
> Key: XERCESJ-1695
> URL: https://issues.apache.org/jira/browse/XERCESJ-1695
> Project: Xerces2-J
> Issue Type: Wish
> Reporter: Nick Ozmore
> Priority: Major
>
> The 2.12 release includes various fixes, including security fixes, which
> Xerces users would like to include in their automated build pipelines. To
> facilitate this it would be very helpful to publish the latest version to
> Maven Center. Currently the latest version available in Maven is 2.11.
> https://mvnrepository.com/artifact/xerces/xercesImpl
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
