Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use libxml-ruby instead of libxml-jruby to fix JRuby test failures. #55

Closed
wants to merge 1 commit into from

Conversation

csw
Copy link
Contributor

@csw csw commented May 15, 2012

The travis-ci Gemfiles currently call for libxml-jruby; this appears
not to support the same API as libxml-ruby, resulting in several tests
in test/unit/bio/db/test_phyloxml.rb failing with "NameError:
uninitialized constant LibXMLJRuby::XML::Parser::Options". Switching
to the C libxml-ruby library allows these tests to pass under JRuby in
1.8 mode.

JRuby in 1.9 mode still fails a few PhyloXML tests due to
https://jira.codehaus.org/browse/JRUBY-6662.

The travis-ci Gemfiles currently call for libxml-jruby; this appears
not to support the same API as libxml-ruby, resulting in several tests
in test/unit/bio/db/test_phyloxml.rb failing with "NameError:
uninitialized constant LibXMLJRuby::XML::Parser::Options". Switching
to the C libxml-ruby library allows these tests to pass under JRuby in
1.8 mode.

JRuby in 1.9 mode still fails a few PhyloXML tests due to
https://jira.codehaus.org/browse/JRUBY-6662.
@csw
Copy link
Contributor Author

csw commented May 15, 2012

It appears that this C extension route isn't going to be supported by JRuby in 1.9 mode. Let's hold off on this for now, I'll look further into alternatives.

@csw
Copy link
Contributor Author

csw commented May 15, 2012

It looks like porting PhyloXML to use Nokogiri instead, and possibly repackaging it as a separate gem, will be the way to proceed.

@csw csw closed this May 15, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant