Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Getting artifacts into Maven Central

I cited CBI because the build team has experience with actually getting bits to Maven Central, not so much about using CBI or the EF instance of Nexus specifically. I'm pretty sure that it's the agreement with Sonatype (and probably the current owners of the namespaces) that we need to sort out.

Wayne

On Mon, Jun 18, 2018 at 1:59 PM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

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@eclipse.org] On Behalf Of Wayne Beaton
Sent: Montag, 18. Juni 2018 16:58
To: EE4J PMC Discussions
Subject: [ee4j-pmc] Getting artifacts into Maven Central

 

Greetings PMC.

 

@waynebeaton What is the technical process to get JAX-RS 2.2 into Maven Central?

 

 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?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.



 

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation


_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top