This project is archived and is in readonly mode.
[patch] Problems with getting version number for java platform gems
Reported by Łukasz Badura | October 8th, 2009 @ 05:01 PM
Currently gem version numbers have to be placed at the end of the directory name which contains the gem. This approach conflicts with the java platform gems e.g. eventmachine-0.12.8-java, and such gems cannot be freezed in the vendor directory. I've prepared a simple patch along with a small update to appropriate test file.
Comments and changes to this ticket
-
Łukasz Badura October 9th, 2009 @ 10:24 AM
- Title changed from “Problems with getting version number for java platform gems” to “[patch] Problems with getting version number for java platform gems”
-
Łukasz Badura October 9th, 2009 @ 02:25 PM
I've a more generic solution. Gem version is determined by a regexp on the directory name. All strings before the version are considered as the name of the gem, after the version as the platform. This approach should also cover e.g. redcloth-x.x.x-universal-java.
-
-
Matt Jones October 16th, 2009 @ 08:39 PM
This fails for prerelease gems (versions like 1.0.1.pre). I don't recall whether those allow dashes in the string part or not, but you may want to check it out.
-
Łukasz Badura January 6th, 2010 @ 04:29 PM
The affected files were removed from the code base, so I guess this ticket is no longer valid ?
-
Rohit Arondekar October 8th, 2010 @ 11:52 AM
- State changed from “new” to “invalid”
- Importance changed from “” to “”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Dominik Grabiec
Jeremy Kemper
Rohit Arondekar
Łukasz Badura
Attachments
Tags
Referenced by
-
3352
gems with running rails with jruby
Closing as a duplicate of #3356.