[
https://issues.apache.org/jira/browse/XERCESJ-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551635#comment-17551635
]
Anthony Cavalliotis commented on XERCESJ-1736:
----------------------------------------------
Hi Team,
As is stands, not publishing an xsd 1.1 artefact to maven central is making
Eclipse ([https://github.com/eclipse/lemminx/pull/515)] and others nervous
about how 'ready' the good work on the codebase you have done.
As a Java developer, lets say I want to start using these xs:assert's defined
10 years ago [https://www.w3.org/TR/xmlschema11-1/] . First I get excited,
because its 10 years ago, tooling should be mature, but then I find in order of
least to most surprise: (1. least) that Notepad++ that uses MSXML and
Microsoft doesn't care to implement W3C these days so my non-tech audience have
to use a Xerces linked editor (to be free); (2) Eclipse IDE (2022-03 version),
a decent choice of free editor, doesn't support due to no library in mvn
central; (3) This ticket is still open on how best to publish a jar (either a
uber-jar or a set of jars); (4) there is still work on this the xerces-J xsd
1.1 codebase (bug fixes) in Jan 2022 (Xerces-J 2.12.2 --
[https://xerces.apache.org/xerces2-j/releases.html)]
Now to correct this state of affairs, I think the only route is to publish to
maven central pronto. Hosting a "on-the-side xsd11library-on-my-website.jar"
is only going to appeal to niche audience and won't give you decent feedback.
Others have tried hosting this –
[https://mvnrepository.com/artifact/org.opengis.cite.xerces/xercesImpl-xsd11/2.12-beta-r1667115]
but it is not the authoritive maven central, which a lot of large
organisations nexus's are backed by.
So if it were me in your shoes/project, I would just create an uberJar
"xercesImpl.jar" (groupId="xerces"; artifactId="xercesImpl") such that the uber
jar embedded the old xsd 1.0 "xercesImpl.jar" and any dependencies of the new
such that the jar could "switch" between implementations based on whether you
asked for SchemaFactory.newInstance("http://www.w3.org/XML/XMLSchema/v1.1";) or
SchemaFactory.newInstance("http://www.w3.org/XML/XMLSchema/v1.0";) and
{*}defaulting to 1.1{*}. That way, you'd offer newcomers a drop-in replacement
to upgrade to xsd 1.1 by simply updating the "version" to say 2.13.0 like below:
<dependency>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId> <!-- new uber jar -->
<version>2.13.0</version> <!-- leave room on 2.12.x until everyone
switches to 2.13.x -->
</dependency>
This way you'd get lots of people using your new features by default and
improve this library faster so that in year 2032 (gasp) we are not in the same
position as I find myself in now.
So anyhow, that is my thoughts. Happy to get involved to publish but think you
are the best placed as when you publish you have to be in a position to bugfix.
I'll watch this for a bit but unless I can get this published and into Eclipse
I think I might have to go the [https://schematron.com/] assert route, but I
didn't really want to add another processing step into the pipeline, both in
code and for users just manually validating in an IDE but might have to.
Thanks for getting this far reading, and the work you've done to-date,
Anthony
> Publish xercesImpl 2.12.2 xml schema 1.1 to Maven Central
> ---------------------------------------------------------
>
> Key: XERCESJ-1736
> URL: https://issues.apache.org/jira/browse/XERCESJ-1736
> Project: Xerces2-J
> Issue Type: Task
> Affects Versions: 2.12.2
> Reporter: Aurélien Pupier
> Priority: Major
>
> currently only the "basic" version is published.
> Might be good to publish the xml schema 1.1 too but what doe sit implies?
> Should it be just a different classifier? or a different groupid/artifactid?
> which ones?
> What is the exact difference, in which case should users use one or the other?
> see request from
> https://issues.apache.org/jira/browse/XERCESJ-1735?focusedCommentId=17483065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17483065
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
