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.

Sign up for GitHub

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

Jump to bottom

Class not found exception on ppc64le #2873

Closed
lbianc opened this issue Apr 24, 2015 · 6 comments
Closed

Class not found exception on ppc64le #2873

lbianc opened this issue Apr 24, 2015 · 6 comments
Labels
JRuby 1.7.x
Milestone
JRuby 1.7.21

Comments

@lbianc
Copy link
Contributor

lbianc commented Apr 24, 2015

I'm building jruby with all fix for ppc64le and there is still a SEVERE message (see below).

@headius I couldn't find from where it is coming, seems it is using jruby 1.7.12, which has not support for ppc64le, probably from there.
Is there something that we could do?

[INFO] ------------------------------------------------------------------------
[INFO] Building JRuby Lib Setup 9.0.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for rubygems:atomic:gem:1.1.2 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ jruby-stdlib ---
[INFO]
[INFO] --- tesla-polyglot-maven-plugin:0.1.1:execute (install_gems) @ jruby-stdlib ---
Apr 24, 2015 3:53:31 PM jnr.ffi.provider.jffi.NativeRuntime buildNativeTypeAliases
SEVERE: failed to load type aliases: java.lang.ClassNotFoundException: jnr.ffi.provider.jffi.platform.unknown.linux.TypeAliases
using jruby 1.7.12
install gems unless already installed

--- gem jruby-readline-1.0 ---
@headius
Copy link
Member

headius commented Apr 27, 2015

Hmm, still not picking up the platform right.

@lbianc
Copy link
Contributor Author

lbianc commented Apr 30, 2015

The SEVERE message is being shown due the use of tesla-polyglot-maven-plugin version 0.1.1, which depends of jruby version 1.7.12. As this JRuby version has not ppc64 support, it will show the message, so we have a cycle dependency.
tesla-polyglot-maven-plugin (0.1.1) seems to no be using ffi (because the build would break) and it's used during the build to read pom files written in Ruby.
This issue will be fixed only when tesla-polyglot-maven-plugin update its jruby dependency to a version that supports ppc64 and the JRuby dependency of tesla-polyglot-maven-plugin version be updated as well.

@mkristian
Copy link
Member

to upgrade this tesla-polyglot-maven-plugin can be done. but to understand @lbianc the build works and the actual SEVERE comes from jruby-1.7.12 which is used the ruby scripts.

@headius
Copy link
Member

headius commented May 8, 2015

@mkristian Can we update tesla-polyglot-maven-plugin to use 1.7.20 now, since that should work ok with ppc64?

@mkristian mkristian reopened this May 8, 2015
@mkristian
Copy link
Member

keep it open until the thing got released

@mkristian
Copy link
Member

fixed with using the new polygot-maven

@enebo enebo added this to the JRuby 1.7.21 milestone Jun 10, 2015
pfrank13 pushed a commit to pfrank13/polyglot-maven that referenced this issue May 27, 2017
@mkristian @pfrank13
use latest jruby-1.7.20 - fixes jruby/jruby#2873
0a2686d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
JRuby 1.7.x
Projects
None yet
Milestone
JRuby 1.7.21
Development

No branches or pull requests
5 participants
@headius @enebo @mkristian @kares @lbianc