Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jgit-dev] FW: [eclipse.org-committers] deploying to Maven Central for Eclipse projects

I requested that the JGit Hudson is configured to enable automatic release deployment to Maven central
in order to simplify the release process

-Matthias

From: <eclipse.org-committers-bounces@xxxxxxxxxxx> on behalf of SAP SAP <matthias.sohn@xxxxxxx>
Date: Friday 19 February 2016 at 16:48
To: Mikaël Barbero <mikael@xxxxxxxxxxx>
Cc: "eclipse.org-committers@xxxxxxxxxxx" <eclipse.org-committers@xxxxxxxxxxx>
Subject: Re: [eclipse.org-committers] deploying to Maven Central for Eclipse projects

this sounds really interesting.
I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=488114  to request this also for JGit.

-Matthias

From: Mikaël Barbero <mikael@xxxxxxxxxxx>
Date: Friday 19 February 2016 at 16:29
To: SAP SAP <matthias.sohn@xxxxxxx>
Cc: Lorenzo Bettini <lorenzo.bettini@xxxxxxxxx>, "eclipse.org-committers@xxxxxxxxxxx" <eclipse.org-committers@xxxxxxxxxxx>
Subject: Re: [eclipse.org-committers] deploying to Maven Central for Eclipse projects

Thanks Matthias. Actually, Lorenzo is deploying from Eclipse to Maven Central thanks to a new process that we are setting up to let project do that without the burden you currently have to do. If you're interested in this process, have a look at https://wiki.eclipse.org/Californium/Signing_Process and open a bug to ask for us to configure your HIPP to let you deploy to maven central.



Sorry Lorenzo I totally missed you bug and message. 

I've closed your repo but it failed with the following erros:

typeId pom-staging
failureMessage Invalid POM: /org/eclipse/emf/parsley/org.eclipse.emf.parsley.parent/0.6.0/org.eclipse.emf.parsley.parent-0.6.0.pom: Project name missing, Project description missing

Let's continue this discussion on your bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=480094

Thanks
Mikael


Le 19 févr. 2016 à 16:13, Sohn, Matthias <matthias.sohn@xxxxxxx> a écrit :

follow http://central.sonatype.org/pages/ossrh-guide.html

For JGit we build the release on Hudson and deploy all artefacts to
Nexus at Eclipse (repo.eclipse.org). Then we use some scripts to download
and deploy the artefacts to Maven central
http://git.eclipse.org/c/jgit/jgit.git/tree/tools/maven-central/download.rb

./download.rb <version>

downloads the artefacts to the local machine and
./deploy.rg <version>
uses maven to deploy them to the Sonatype OSS staging repository

The staging repository on https://oss.sonatype.org/ is created on the fly
when you deploy the artifacts. You then can inspect the repository online.
If anything is wrong drop it and start over. Otherwise close the staging
repository in Nexus UI, this will run consistency checks on all the artefacts.
When closing was successful you can find the URL of the staging repository
in the Nexus UI. Then you can test if the artefacts are ok and release the
staging repository if they are good. To my experience replication to Maven
central can take a while.

-Matthias

On 18/02/16 17:39, "eclipse.org-committers-bounces@xxxxxxxxxxx on behalf of Lorenzo Bettini" <eclipse.org-committers-bounces@xxxxxxxxxxx on behalf of lorenzo.bettini@xxxxxxxxx> wrote:

Hi

We managed to perform the first maven release, but now it is not clear
how to promote the staging repository for the release.  I find no such
staging repository on Sonatype Nexus.

thanks in advance
Lorenzo

On 12/10/2015 10:20, Mikael Barbero wrote:
Hi Lorenzo,

We provide an alternative procedure. It is outlined in
bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=468448 and https://wiki.eclipse.org/Californium/Signing_Process.
This is about Californium but we plan to make this thing available to
any project (Californium really is just starting to use it, but the
procedure is quite well defined now). If you want to do such a thing,
just open a bug against community and ask us to create a project
specific account at ossrh and gpg signing keys for your project.

Thanks.
Mikael

Le 10 oct. 2015 à 18:07, Lorenzo Bettini <lorenzo.bettini@xxxxxxxxx
<mailto:lorenzo.bettini@xxxxxxxxx>> a écrit :

Hi

we would like to start deploying Maven artifacts for our Eclipse
project on Maven central.  Should we follow the standard procedure
required by Maven central or does the Eclipse infrastructure provide
an alternative procedure?

I could not find this information in the Eclipse wiki...

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

_______________________________________________
eclipse.org <http://eclipse.org>-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
<mailto:eclipse.org-committers@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/eclipse.org-committers

IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.



--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-committers

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.








_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-committers

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top