isXander / isXander/YetAnotherConfigLib
Common jars being remapped when they should'nt be
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 155
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Published "common" jars for this library are remapped, while architectury remaps these jars correctly for arch-common projects, projects making use of fabric-loom/vanilla-gradle break as the jar is not remapped correctly.
This can be fixed by not shipping remapped jars for "common", remapping is only really required when being run in production, as "common" is a dev-time only jar it is safe to never remap the jar.
Error example
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
No file or test is named. Start by locating the publishing and remapping configuration for the library's common jars, then reproduce the issue with a fabric-loom or vanilla-gradle consumer. Done means common jars are published without remapping while production artifacts retain the required behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100