maven gem support does allow to install all possible maven artifacts
--------------------------------------------------------------------
Key: JRUBY-5452
URL: http://jira.codehaus.org/browse/JRUBY-5452
Project: JRuby
Issue Type: Bug
Affects Versions: JRuby 1.6RC1
Reporter: kristian meier
Assignee: Thomas E Enebo
Priority: Minor
Attachments: 0001-use-mvn-as-prefix-for-all-gemnames.patch,
0002-allows-add-repos-from-source-as-well.patch,
0003-specs-follow-changes-in-maven_gemify.patch
$ jruby -S gem list -r joda-time:joda-time
*** REMOTE GEMS ***
joda-time:joda-time (1.6.2 java, 1.6.1 java)
but a look into the maven central repository shows that the correct answer is:
$ jruby -S gem list -r mvn:joda-time:joda-time
*** REMOTE GEMS ***
mvn:joda-time:joda-time (1.6.2 java, 1.6.1 java, 1.6.0 java, 1.5.2 java, 1.5.1
java, 1.5.0 java, 1.4.0 java, 1.3.0 java, 1.2.1 java, 1.2.0 java, 1.1.0 java,
1.0.0 java, 0.95.0 java)
there are even artifacts which do not have a single version which can be
installed:
$ jruby -S gem list -r com.unboundid:unboundid-ldapsdk
*** REMOTE GEMS ***
but there indeed quite a few version of that artifact and it should be
$ jruby -S gem list -r mvn:com.unboundid:unboundid-ldapsdk
*** REMOTE GEMS ***
mvn:com.unboundid:unboundid-ldapsdk (2.0.1 java, 2.0.0 java, 1.1.6 java, 1.1.5
java, 1.1.4 java, 1.1.3 java, 1.1.2 java, 1.1.1 java, 1.1.0 java)
this is fixed with underlying gemify-maven-plugin version 0.24.0 but rubygems
need to switch to it. the attached patches are made against branch
origin/jruby-rubygems_1_4_2 of jruby/rubygems but should apply to 1.5.0 as well
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
