processing / processing/processing4
Need better method than reflection for setting application name on Linux
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Created by: benfry
Inside LinuxPlatform, we're using reflective access to set the application name. Not a great idea but a well-known hack. This started throwing a nasty warning (that kinda looks like an error) on startup with Java 11 and 17.
That's been fixed with https://github.com/processing/processing4/commit/8e5433430e266592b83da0a68542d4d082738c38, which resolves https://github.com/processing/processing4/issues/207, which covers the warning itself.
Another detailed thread from folks looking into the same issue: https://github.com/cryptomator/cryptomator/issues/956#issuecomment-787061581
…but we need a better solution longer-term. Please help?
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
LinuxPlatform is the only code entry point named; start by locating it and reviewing the linked commit 8e5433430e266592b83da0a68542d4d082738c38, issue 207, and the Cryptomator discussion. Done means replacing the reflective application-name approach with a suitable Linux solution without the Java 11/17 startup warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100