Deploy One-JAR to Maven Central
Status: Beta
Brought to you by:
simontuffs
Menu
▾
▴
#5 Deploy One-JAR to Maven Central
I am developing a Gradle one-jar plugin, like the one for Maven, but cannot find the jar on Maven Central. I see that the Maven plugin has included the jar inside itself, but as I would like to make it possible to choose which version of One-JAR to use, I don't think including is a good solution.
Therefore, would it be possible to deploy the jar to Maven Central?
Regards,
Stig Kleppe-Jørgensen
That sounds like a good idea. I did not develop or deploy the maven jar, I'd have to look into this. Alternatively if you have suggestions on the best way to do this, I'd be happy to have you upload the latest (0.97) jar to the maven repos, and collaborate with you as the jar is updated.
Yes, I have some suggestions :-)
In short, here is what is needed for deploying to Maven Central:
- a pom.xml describing the project
- 3 jars with classes, sources and javadocs
- GPG signing of the jars and the pom.xml
There is an Ant task available for doing this. The whole how-to is here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7c.DeploySnapshotsandStageReleaseswithAnt
I would like to help out with setting up this. Though it might be best that you run the actual upload, so the signing is done with your GPG key.
Another thing, have you thought about converting the repository to git? Makes collaboration quite a bit easier...
I pushed a fork of the whole one-jar cvs module to GitHub (http://github.com/stigkj/one-jar) as I have some changes I would like to work on.
As these are based off of the version_0_9_6_RC5 tag and I would like to eventually get these merged into master, it seemed easier to convert the whole repo to git than working with cvs.
By the way, as of right now, my changes are not pushed to GitHub yet, because they are not in a publishable state.
Thanks for pushing forward with this. I'm not thrilled with GIT, I have used various SCM tools starting with CVS, through Subversion and P4, and I think Subversion has the best fit with my mental model, and might be a better fit for me for One-Jar. My one experience with GIT (not extensive I'll admit) was basically, this is very powerful, unconstrained, confusing, and impossible to useI abandoned it. I'm willing to revisit this.
Since One-Jar is on source-forge and I'd prefer to keep it that way, and as far as I know Source-forge is Subversion/CVS based, how can we get you the advantages of GIT without making it difficult for me?
I understand your sentiments, git is absolutely not the easiest tool to get one's head around. I think it would be easier if one did not have any previous experience with a non-distributed VCS, like CVS/Subversion. As Joel Spolsky says, for Subversion users, a re-education is needed (see http://hginit.com/00.html; this is Mercurial, but the concepts are the same).
What I like best about it, is the ability to do many commits, revisit and maybe fix them (edit comment, edit/squash/remove commits), before sharing my work with others. Working locally is great: search code & logs, change between branches, etc. And something I don't think about this much anymore, not until I must work with CVS/Subversion: its speed. It is just amazing to see it clone a project faster than a single checkout would have taken in Subversion
Sorry, got carried away there :-) I thought I had read that SourceForce had gotten git support, so I tried to create a project and add git. It worked: http://metest.git.sourceforge.net/git/gitweb-index.cgi
But of course, it is your decision. I can use something like git-svn to work with git locally and sync with a Subversion repository. One-JAR is still in CVS though, is it not? And you have a plan to convert it to Subversion?
I'd like to see the one-jar runtime support in the maven repo, too. Thanks!