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

JDK9 + 1.7.x produces io/console warnings #3611

Closed
headius opened this issue Jan 21, 2016 · 3 comments
Closed

JDK9 + 1.7.x produces io/console warnings #3611

headius opened this issue Jan 21, 2016 · 3 comments
Milestone
Invalid or Duplicate

Comments

@headius
Copy link
Member

headius commented Jan 21, 2016

Not sure why these warnings are coming up.

$ jruby -v -e 1
jruby 1.7.25-SNAPSHOT (1.9.3p551) 2016-01-21 592384a on Java HotSpot(TM) 64-Bit Server VM 9-ea+100-2016-01-06-200131.javare.4235.nc +jit [darwin-x86_64]
failed to load native console support: Unsupported platform: x86_64-darwin
io/console not supported; tty will not be manipulated
...

We need to make fixes to 1.7 to support JDK9's new platform/version strings, I assume. We already made these changes on master.
@headius headius added this to the JRuby 1.7.25 milestone Jan 21, 2016
@headius headius changed the title JDK9 + 1.7.x produces io/console warnings when run through rvm JDK9 + 1.7.x produces io/console warnings Jan 21, 2016
@enebo enebo modified the milestones: JRuby 1.7.26, JRuby 1.7.25 Apr 8, 2016
@headius headius mentioned this issue Aug 24, 2016
Closed
2 tasks
@headius headius modified the milestones: JRuby 9.2.0.0, JRuby 1.7.26 Aug 24, 2016
@iignatev iignatev mentioned this issue Mar 29, 2017
Merged
@perlun
Copy link
Contributor

perlun commented Oct 5, 2017

JRuby 1.7 has reached EOL (#4112). Can we close this?

@mprins
Copy link
Contributor

mprins commented Oct 5, 2017

this may be a duplicate of #3700

@enebo enebo removed the JRuby 1.7.x label Oct 5, 2017
@enebo
Copy link
Member

enebo commented Oct 5, 2017

Yeah we will not support Java 9 for 1.7.x and this issue was fixed on 9.x before this issue was even opened. So I will close this.

@enebo enebo closed this as completed Oct 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Invalid or Duplicate
Development

No branches or pull requests
4 participants
@headius @enebo @perlun @mprins