bad gem file creation using mode --1.9
--
Key: JRUBY-6208
URL: https://jira.codehaus.org/browse/JRUBY-6208
Project: JRuby
Issue Type: Bug
Components: Ruby 1.9.2
Affects Versions: JRuby 1.6.5
Hash#rehash does not work under some condition
--
Key: JRUBY-6209
URL: https://jira.codehaus.org/browse/JRUBY-6209
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affe
Hi there,
I recently had some problems with jar dependencies in jRuby and tried to find
the most elegant solution.
IMHO the "gem install mvn:" feature is brilliant.
The only missing thing is bundler support.
Bundler is not able to find the gems because they're not included in the #list
result, w
hi,
first I need to express my point of view about jruby and
classloaders/classpath, etc and that I did in blog post of mine:
http://blog.mkristian.tk/2011/09/jruby-and-rubygems-and-javaclassloader.html
sonatype.org worked on a nexus plugin which can offer a maven
repository as rubygems-reposito
Has anyone looked at the Sonatype Aether plugin(http://aether.sonatype.org/)?
I've been following along with Clojure's Leiningen project, and they are
moving their own system to using Aether for dependency management, as it
handles all of the Maven settings, proxies, repository/dependency
resoluti
maybe, not sure if aether is really sufficient. probably it is enough
for something like adding
jar 'slf4j:simple', '2.6.2'
in your Gemfile and let aether resolve all deps for it.
but I would like at put one more feature of ruby-maven into the discussion:
you can declare jar-dependencies in you
Hi,
I've seen Kristians blogpost and I greatly appreciate his work.
I already thought about writing him a personal email before writing to this
list.
As I'm using Buildr, I wanted an build system independent solution.
I like the way jars are installable by default, even if it seems rather
"Hacki
first I need to point you to
http://jpkutner.blogspot.com/2011/04/ease-of-bundler-power-of-maven.html
the author has bundler integration.
I guess my last point to Nick email is to point out problems like:
Gemfile:
source :rubygems
gem 'nokogiri'
gem 'mvn:xerces:xercesImpl', '3.1.0'
with such
Hi Kristian,
its my understanding that if nokogiri would name its mvn dependencies (in the
gemspec),
bundler would wipe out this problem and only one version of xercesimpl would be
active.
The only problem left is that buildr (in my case) would use different gems.
This is no problem at all (f
