| Re: [ee4j-pmc] Getting artifacts into Maven Central |
I have experience with publishing to Maven Central using OSSRH. If we want to use CBI instead, the EF has to find an agreement with Sonatype, just like the ASF has one. At least this is told on their web site. HTH -Markus From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton Greetings PMC.
Can we please add this to our agenda for our next call? Frankly, I have no direct experience with this. I'm pretty sure that we can get the Common Build Infrastructure (CBI) team to help, but we'll need to help them understand all of the issues. I have a recollection of there being a challenge with regard to using the namespace that we may have to help address. Whatever we sort out, we should document. Wayne On Sun, Jun 17, 2018 at 9:22 AM, Markus KARG <notifications@xxxxxxxxxx> wrote: @chkal While I certainly think Sanstiago's opinion is very relevant to this question, I need to object that it is him to finally decide. According to the Eclipse Handbook (https://www.eclipse.org/projects/handbook/#pmi-commands-release) all committers can trigger a release; I couldn't find a chapter telling about any special role of project leads in this regard. Hence I would propose that all committers perform a democratic voting. @m0mus Is the PMC forcing us to write new specification documents prior to a minor feature release, or is it allowed to do a JAX-RS 2.2 release without spec PDFs? @waynebeaton What is the technical process to get JAX-RS 2.2 into Maven Central? — -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation |