jMonkeyEngine / jMonkeyEngine/sdk
The Mac OS JDK Symlink Issue
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
So, see 32ecc255d11b29f9727ed64cad9230e6a9666abd and the faults on travis https://travis-ci.org/jMonkeyEngine/sdk/jobs/631935705#L2083
We need to resolve symlinks, e.g. like in https://stackoverflow.com/a/7167623
For this, we need to evaluate the JDK before and afterwards (e.g. does it work without the links, what does it affect?)
Currently it appears to me that it's only used for Licenses and Manuals, where we could afford duplication, but it might change with every release without us noticing.
I don't have much confidence in Apache fixing this in Ant though, because of this
Contributor guide
No contributing guide indexed for this repository
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
Review commit 32ecc255d11b29f9727ed64cad9230e6a9666abd and the linked Travis failure first. Trace how the JDK is evaluated for Licenses and Manuals, then compare behavior before and after resolving symlinks. Done means the Mac OS JDK path works without breaking the affected release contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100