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]> 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]."; > > > > 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] > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
