Is Xerces a commercial product ?
Is Xerces a library ?
Is Xerces a de facto standard implementation ?
How many projects depend on Saxon-EE ?
How many projects depend on Xerces ? Much more, I beleive.
But, if I are not going to publish Xerces 2.12 on Maven Central, no
project will depend on Xerces, xerces will become an unused standard
implementation, and project pruposes are missed : being a reference
implementation, widely used.
Xerces is used everywhere, at least at a low-level parsers
implementation, mainly in non-xml teams. XML Teams are able to choose
exactly which library they want to use, it is their business. But all
teams with no XML skills are not enough advised to choose exactly which
library to use. And they will only rely on what's available on simplest
place to find a library : search.maven.org
So, you are right, if you want to keep Xerces 2.12 unused, just
distribute it from ASF web sites ; but I think Xerces use is much wider
than this, and deserves to be distributed on maven central.
As you mention, I'm able to put it on my own Nexus, but as a XML coder,
I'm not your target.
How could you be able to motivate contributors to participate, if the
final delivery is not delivered to MAven Central ?
Do as you believe the best.
Christophe
Le 18/06/2018 à 14:46, Mukul Gandhi a écrit :
for example, if anyone is developing a commercial java binary, then is
it mandatory to distribute it on Maven Central? I don't think so. If
you'll buy a java jar from a vendor, you'll likely not get it on Maven
Central. The vendor would ask you to download it from their http / ftp
site. As a specific example, Saxon-EE is not published on Maven
Central. How that is different from how we distribute jars just now?
Regards,
Mukul Gandhi
On Mon, 18 Jun 2018, 17:16 Christophe Marchand, <[email protected]
<mailto:[email protected]>> wrote:
Mukul,
Maven central is de facto the place where deliveries go. If
someone can
not find a jar in maven central, then it is not available, even if it
has been released on project's web site.
Everybody knows exactly how to publish a jar on a local - or
enterprise
- repository. It is a bad practise - each organization is responsible
for publishing their artifacts ; I'm nto going to take
responsability to
publish somenthing I didn't build.
Previous releases of xerces are in maven central, the last release
*must* be also published to maven central.
Publishing to maven central is a very simple job. And it says
"this is
the official release", all other are non-official publications,
and so
should not be used.
I can take the official xerces publication, and release it under a
groupId I own. I will be available on maven central, but it's not
going
to be the *official* one.
Or maybe it is an official position of Apache to not deliver their
artifacts on Maven Central and let people deploy their own - maybe
wrongly built.
Thanks a lot for links on Maven documentation. I suggest you to read
this one :
https://maven.apache.org/repository/guide-central-repository-upload.html
Hope we'll quickly be able to find xerce 2.12.0 in maven central.
Best regards,
Christophe
Le 18/06/2018 à 13:06, Mukul Gandhi (JIRA) a écrit :
> [
https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515588#comment-16515588
]
>
> Mukul Gandhi commented on XERCESJ-1695:
> ---------------------------------------
>
> I had written earlier about this issue in another thread, a
while ago. I'm again writing it below,
>
> "it should be possible to install Xerces 2.12.0 jars in the
local Maven repository by users, and have Xerces jars function as
Maven project dependencies. Following documentation, explains how
to do this,
[https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html]
<https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html%5D>."
>
> In the context of this bug report/wish, if any jar is not
available in Maven central, it can be converted locally into Maven
dependency for the project (that's what the above paragraph
tells). If all this is not understood, IMHO you'd need to learn
Maven basics.
>
>> 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]
<mailto:[email protected]>
> For additional commands, e-mail: [email protected]
<mailto:[email protected]>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
