truffle artifacts are not on maven central and we have a release repo in jruby-parent.pom

[mkristian]

this actually is a follow up to #2466

currently the regular maven artifact 'org.jruby:jruby-core' does not work since it depends on truffle artifacts which are NOT on maven central.

the release repo for the truffle in jruby-parent.pom is a no way, we can not deploy such artifact via sonatype since maven central should stay self contained.

[mkristian]

@chrisseaton right now we can NOT release jruby with truffle as is

[chrisseaton]

Yeah - we'll see what we need to do to get on Maven Central. JRuby goes via Sonatype, right? How does it do that?

[headius]

@chrisseaton This guide should give you all you need to know to get an organization/groupId/artifactId using Sonatype's OSS support: http://central.sonatype.org/pages/ossrh-guide.html

This is the same setup all our JRuby-related artifacts use.

[headius]

This has been mitigated by temporarily pushing a truffle artifact on com.headius groupid. We'll revert back to the Oracle jars once they've been pushed to maven central.

[headius]

Truffle is in maven central now.