jMonkeyEngine / jMonkeyEngine/jmonkeyengine
JBullet JAR is not properly included as a Maven artifact
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
When uploading maven artifacts, the jbullet and stack-alloc jars are not considered at all. They are not marked as a dependency of the jme3-jbullet artifact nor are they uploaded to the repository via the uploadArchives task.
This should be easily fixable if somehow those jars can be considered as "built from source" from gradle point of view, then all that is needed is to specify a project + configuration dependency instead of a jar file dependency inside the jme3-jbullet build script.
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
Start with the jme3-jbullet build script and trace how the jbullet and stack-alloc JAR dependencies are declared, then inspect the uploadArchives task. Done means the generated Maven metadata marks both JARs as dependencies and the artifacts are uploaded to the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100