Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.6RC1
-
Fix Version/s: JRuby 1.6RC1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Pretty ugly error output when gemify can't get a list of artifact versions:
https://gist.github.com/708640
In this case it appears to be a bad POM, and the maintainers have been notified. However I ran into the same problem with other java.net projects, so it's not uncommon. We should at least not blast Java backtraces at the user (without gem --backtrace or whatever the flag is, anyway), and perhaps can handle this more gracefully.
This is perhaps as much a gemify bug as a rubygems/maven bug.
Issue Links
- is related to
-
JRUBY-5217
RubyGems Maven doesn't like alphanumeric versions
-
there are more issues in here.
the reported one can be reproduced with
the second one is the java stacktrace
the next one is
where there is no jar file on maven-central due to license issues or so, but the pom has a download-url to fetch the jar. maven ask you then to install the jar manually.
how shall rubygems handle such a situation ?