Gem dependencies with '~> 0' result in '[0,0]'

Created by: jkutner

When adding a pom.xml dependency on a rubygem that has a dependency of ~> 0 on another gem, Maven fails with an error like:

[ERROR] Failed to execute goal on project heroku-buildpack-java: Could not resolve dependencies for project com.heroku:heroku-buildpack-java:pom:1.0-SNAPSHOT: Failed to collect dependencies at rubygems:heroku_hatchet:gem:1.3.4 -> rubygems:heroku-api:gem:[0,0]: No versions available for rubygems:heroku-api:gem:[0,0] within specified range -> [Help 1]

I've also found that this is a problem when using a pom goal on a gemspec to generate a pom.xml. The resulting pom file will have a [0,0] dependency.

I've created two projects under gem-maven-plugin/src/it to reproduce these, but I can't seem to figure out how to fix them. I've looked a spec2pom.rb but didn't have any luck. Can you point me in the right direction?