please publish an up-to-date release on maven central

[bimargulies]

Currently, central has an old version, and java.net has a newer version with a missing pom. Could you please use ossrh to publish the current version to central? If you're not willing, would you mind if I used the bundle publication process to do it?

[dwdyer]

The only Maven repository I've ever published to is the Java.net one, so I don't know where the one on central came from. I've not been able to publish to Java.net since they migrated to the new infrastructure, it just doesn't work for me.

I'm not a Maven user myself so I'm not familiar with ossrh or the bundle publication process. I'm happy for you to re-publish the artifacts wherever you need them to be.

[bimargulies]

I can take it from here.

On Apr 7, 2011, at 4:45 PM, dwdyer
[email protected]
wrote:

The only Maven repository I've ever published to is the Java.net one, so I don't know where the one on central came from. I've not been able to publish to Java.net since they migrated to the new infrastructure, it just doesn't work for me.

I'm not a Maven user myself so I'm not familiar with ossrh or the bundle publication process. I'm happy for you to re-publish the artifacts wherever you need them to be.

Reply to this email directly or view it on GitHub:
#1 (comment)

[bimargulies]

Dan,

I've started the wheels in motion to push 1.2.2. I can also set things up for you to publish via the Sonatype OSSRH repo (which automatically goes to central). You have this 'uncommons' antlib that must be specific to java.net. Given the gpg requirements for sonatype, the easiest thing is really a shell script that runs a couple of maven commands to do the dirty work. I can drop that into a fork and send you a pull request.

--benson

[dwdyer]

Thanks for doing this. I'll take a look at merging it sometime in the next couple of days.

[bimargulies]

You're welcome. I had a bit of trouble getting out of my own way, and I have a little mopping left to do. The pushes of 0.6.2 of watchmaker are fine, and 1.2 of maths. I pushed 1.2.2 twice due to confusion on my part. '1.2.2' has a broken dependency on jfreechart; '1.2.2a' has a working dependency, but I should never have put it there in the first place. I'll push a 1.2.2b that takes the dependency again.

[eyealike]

I don't understand. If 1.2.2a has the correct dependency why did you want to push 1.2.2b? Anyways, 1.2.2b was never pushed, at least I can't find it on [1]. Between 1.2.2 and 1.2.2a, which one should I use?

[1] http://mvnrepository.com/artifact/org.uncommons.maths/uncommons-maths

[cowwoc]

Any update on this?

[dwdyer]

@cowwoc What are you looking for (a 1.2.3 release on Maven Central?)

I'm looking at the pull request from @bimargulies now (#2). It says I need permission to publish to the org.uncommons group ID. How do I get that permission?

[cowwoc]

I've personally followed these steps: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

You take ownership of the org.uncommons group ID by filing a JIRA issue as mentioned in step 3. Let me know if you have any questions and I will try to answer them.

[benson-basis]

After all this time, I don't even remember why I wanted this, and I don't need it any more. Don't do any work here on my behalf.

[dwdyer]

@cowwoc Thanks. I have created the JIRA issue here: https://issues.sonatype.org/browse/OSSRH-6063

@benson-basis No problem, I should have dealt with this when you originally opened the issue but I completely forgot about it.

[cowwoc]

@dwdyer I believe this issue should closed.

[slandelle]

@cowwoc Why? The only uncommon-maths 1.2.3 artifacts deployed on central are the ones I deployed in my project's groupId (io.gatling), not org.uncommons. Note that I also deployed a Java 6 compatible version (jdk6 classifier).

[cowwoc]

This issue was created before org.uncommons.maths was ever published to Maven Central. It dealt with creating such a groupId and as such should be closed.

Publishing newer releases is out of scope for this issue and separate issues should be opened. Issue #10 already covers version 1.2.3.

[slandelle]

ok