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

Don't use Sun internal APIs - Signal & SignalHandler #27

Closed
GoogleCodeExporter opened this issue Oct 1, 2015 · 3 comments
Closed

Don't use Sun internal APIs - Signal & SignalHandler #27

GoogleCodeExporter opened this issue Oct 1, 2015 · 3 comments
Labels
auto-migrated Milestone-1.1 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Rather than documenting that a valid warning should be ignored, the code 
should be fixed to not use private Sun classes.  The attached patch uses the 
supported Runtime.addShutdownHandler API instead.

It has *not* been tested.

Original issue reported on code.google.com by tfmorris on 13 May 2010 at 7:58

Attachments:
@GoogleCodeExporter
Copy link
Author 

applied at r756

Original comment by stefano.mazzocchi@gmail.com on 13 May 2010 at 9:03

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by tfmorris on 18 Sep 2012 at 2:21

  • Added labels: Milestone-2.0

@GoogleCodeExporter
Copy link
Author

Original comment by tfmorris on 18 Sep 2012 at 2:56

  • Added labels: Milestone-1.1
  • Removed labels: Milestone-2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-1.1 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter