versions since 1.1.14 have not been published on maven central

[tamird]

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jruby.rack%22%20AND%20a%3A%22jruby-rack%22

can someone fix this?

[kares]

simply because there's none since ... you're welcome :)

[kares]

also here's the to-do for 1.2 if you're eager for new versions: #168

[tamird]

1.1.16 is published on codehaus though

[mkristian]

I will see if I can push the artifact to maven-central via jruby
sonatype.org account.

[kares]

well it should not matter as long as it's synced to central right or am I missing something ?
we've talked about it with @mkristian previously, but maybe some things changed that I am not aware of.

if it's to be changed and existing users are to be affected, maybe we shall only switch master and not the 1.1 stable branch.

[mkristian]

@kares I was talking about taking the jar from the gem and deploy it
manually to oss.sonatype.org and then release it to maven central. the next
step is to set up sonatype inside pom.xml of master branch.

On Sat, Nov 15, 2014 at 11:11 AM, Karol Bucek [email protected]
wrote:

well it should not matter as long as it's synced to central right or am I
missing something ?
we've talked about it with @mkristian https://github.com/mkristian
previously, but maybe some things changed that I am not aware of.

if it's to be changed and existing users are to be affected, maybe we
shall only switch master and not the 1.1 stable branch.

—
Reply to this email directly or view it on GitHub
#187 (comment).

[kares]

@mkristian oh, I have not realised you'll planning to do that ... still not get what it is good for. but as long as the release is still possible with mvn than I do not care since you know the beast called Maven better.

[mkristian]

@kares I did not touch the git repo, just picked what I need to create
this:
https://oss.sonatype.org/content/repositories/orgjruby-1052/org/jruby/rack/jruby-rack/1.1.16/
and I am about to press the button "release to maven central"

I did miss the the jruby-rack-1.1.16 artifact on maven central a week ago
or so since I am usually not using warbler just maven to build my ruby wars.

from my side you can close the ticket - the jar are on the way to
maven-central

[kares]

OK, but since its deployed there we'll probably need to do smt about this ... is it a standard sonatype deployment or do I need some setup, also who's setting up deploy rights under the jruby org (guessing @enebo) ? we'll probably end up pushing 1.1.x mvn artifact 2 ways (for compatibility) and for master we'll switch to sonatype only ... unless someone points out no to do so :)

[mkristian]

@headius did arrange the deployment rights on sonatype.org for groupId
'org.jruby' - I arrange to get the permissions for groupId 'rubygems' for
the jruby team. so I guess ping @headius about 'org.jruby.rack' groupId (or
even org,jruby)
and maybe 'rubygems' so you can push jruby-openssl gem snapshots to
sonatype as well !

let's just switch over to use sonatype.org - the setup is very easy and I
will prepare a PR for the 1.1-stable branch right now (since I am in that
maven mode already).