{"action":"created","issue":{"url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/41","labels_url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/41/comments","events_url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/41/events","html_url":"https://github.com/asciidoctor/asciidoctor-maven-examples/issues/41","id":124025445,"number":41,"title":"Add an example that consume a ruby gem as extension","user":{"login":"jmini","id":1222165,"avatar_url":"https://avatars.githubusercontent.com/u/1222165?v=3","gravatar_id":"","url":"https://api.github.com/users/jmini","html_url":"https://github.com/jmini","followers_url":"https://api.github.com/users/jmini/followers","following_url":"https://api.github.com/users/jmini/following{/other_user}","gists_url":"https://api.github.com/users/jmini/gists{/gist_id}","starred_url":"https://api.github.com/users/jmini/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmini/subscriptions","organizations_url":"https://api.github.com/users/jmini/orgs","repos_url":"https://api.github.com/users/jmini/repos","events_url":"https://api.github.com/users/jmini/events{/privacy}","received_events_url":"https://api.github.com/users/jmini/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/labels/tracking","name":"tracking","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-12-28T06:42:44Z","updated_at":"2016-01-14T23:07:12Z","closed_at":null,"body":"This was first mentioned in #27. It is great to have as example a maven project that consumes a ruby gem as extension (using the TorqueBox RubyGems Maven Proxy Repository):\r\n\r\n> we will need another sub-project to show how to integrate ruby extensions\r\n\r\nFor the moment, `asciidoctor-pdf-with-theme-example` is using it, until #40 is fixed.\r\n\r\nThis issue keeps everything together:\r\n\r\n* Mailing list: [asciidoctor-html5ruby broken?](http://discuss.asciidoctor.org/asciidoctor-html5ruby-broken-td4081.html)\r\n* Example with ` asciidoctor-pdf-cjk` in [asciidoctorj/#412](https://github.com/asciidoctor/asciidoctorj/issues/412#issuecomment-165040508)\r\n* When the gem library declares version ranges as dependency (this is the case for `asciidoctor-bibtex`), maven downloads each version in each range. Some of those versions declare broken dependency which produces this maven error \"Failed to collect rubygems dependencies!\". This is documented in [jruby-maven-plugins/#57](https://github.com/torquebox/jruby-maven-plugins/issues/57). The solution is to declare each precise gem version in the `<gems>` section of the configuration.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/comments/171810511","html_url":"https://github.com/asciidoctor/asciidoctor-maven-examples/issues/41#issuecomment-171810511","issue_url":"https://api.github.com/repos/asciidoctor/asciidoctor-maven-examples/issues/41","id":171810511,"user":{"login":"abelsromero","id":5781153,"avatar_url":"https://avatars.githubusercontent.com/u/5781153?v=3","gravatar_id":"","url":"https://api.github.com/users/abelsromero","html_url":"https://github.com/abelsromero","followers_url":"https://api.github.com/users/abelsromero/followers","following_url":"https://api.github.com/users/abelsromero/following{/other_user}","gists_url":"https://api.github.com/users/abelsromero/gists{/gist_id}","starred_url":"https://api.github.com/users/abelsromero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abelsromero/subscriptions","organizations_url":"https://api.github.com/users/abelsromero/orgs","repos_url":"https://api.github.com/users/abelsromero/repos","events_url":"https://api.github.com/users/abelsromero/events{/privacy}","received_events_url":"https://api.github.com/users/abelsromero/received_events","type":"User","site_admin":false},"created_at":"2016-01-14T23:07:12Z","updated_at":"2016-01-14T23:07:12Z","body":"I'm not sure `bibtex` can be integrated as it is. I get the following error:\r\n```\r\nFailed to collect dependencies at rubygems:citeproc-ruby:gem:1.1.0 -> rubygems:citeproc:gem:1.0.2 -> rubygems:namae:gem:0.8.2 -> rubygems:rubysl:gem:2.0.8 -> rubygems:rubysl-json:gem:[2.0,2.99999]: No versions available for rubygems:rubysl-json:gem:[2.0,2.99999] within specified range -> [Help 1]\r\n```\r\nAnd when I force the url in rubygems it says that the gem is no longer available https://rubygems.org/gems/rubysl-json.\r\nAlso, tried the exclude namae and add a newer version, but the error persists.\r\nBefore reporting why the exclusion/inclusion does not work to the gem-maven-plugin, I opened a request to bibtex to see if he cap upgrade the dependencies to newer versions.\r\nhttps://github.com/ProgramFan/asciidoctor-bibtex/issues/4\r\n"}}