Konloch / Konloch/bytecode-viewer
Java 17
Open
Nobody has claimed this yet.
Bug
Discussion
- Dominant language
- Java
- Stars
- 15.6k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Java 17 deprecated the SecurityManager and so, we should plan to move on somehow... But how?
As far as I know, there is no real replacement for the SecurityManager, which will make this change pretty hard.
Maybe, it's just best to ignore the warning?
For more information, here is the warning:
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by the.bytecode.club.bytecodeviewer.BytecodeViewer (file:/F:/Misc/SelfBuilt/bytecode-viewer/target/classes/)
WARNING: Please consider reporting this to the maintainers of the.bytecode.club.bytecodeviewer.BytecodeViewer
WARNING: System::setSecurityManager will be removed in a future release
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a source file or test. Start by locating the System.setSecurityManager call in the Java sources, then review how it is used and the available Java 17 alternatives. Done means the deprecated usage is addressed and the warning no longer occurs, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100