On Thu, Oct 13, 2011 at 5:03 PM, Luis Lavena <luislav...@gmail.com> wrote: > 1) Gem names with ":" will not work on Windows, is not safe.
I'll look into that. I know we have tests for this functionality that pass on Windows... > 2) RubyGems cannot install gems across multiple repositories (so if > your maven wrapper is in another server it will not find it) The Maven logic is built into our copy of RubyGems directly; it knows if it sees anything prefixed with "mvn:" it uses Maven to source the contents of that gem, rather than looking on rubygems.org. > 3) Last but not least: let's not turn RubyGems "dependencies" into > "anything this gem depend on". How would you recommend people grab the required libraries? Like I said in other posts, I can certainly recommend that they start wrapping and pushing those libraries to rubygems.org, but I don't think anyone wants rubygems.org bloated up with thousands of jar files. > RubyGems dependencies *must be* a gem. These *are* gems...we just build them dynamically by sourcing the contents from Maven. - Charlie _______________________________________________ RubyGems-Developers mailing list http://rubyforge.org/projects/rubygems RubyGems-Developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
