jMonkeyEngine / jMonkeyEngine/sdk
assets issue in gradle projects
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
i've encountered an issue (3.8.0). i have two gradle projects with assets open in the sdk. sometimes the first one's assets are replaced by the second ones. but the folder structure on the hdd is correct.
it happened again. this time i got a warning that the asset was not on the project path (or something similar). i then tried to open a model (in the assets project) and got the same message.
i then looked at the project assets folder in the main project, and they had the files from another open project.
restarting "resolved" the issue.
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
Reproduce the issue by opening two Gradle projects with assets in the SDK, then inspect each project's asset folder after switching between projects. Check the asset-path warning and whether files from one project appear in the other; done means both projects consistently retain their own assets without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100