Classifier ignored for statically linked libraries
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 268
- Forks
- 196
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 10
Description
It seems to be that since 2.0.50.Final its not possible to get just the specified classifier as per the wiki which results only the full Uber jar downloaded
Behavior <= 2.0.49.Final
Behavior after >= 2.0.50.Final
This is the pom.xml dependencies
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>2.0.63.Final</version>
<classifier>linux-x86_64</classifier>
</dependency>
Behavior is the same with ${os.detected.classifier}
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 pom.xml dependency shown in the report and compare classifier resolution between 2.0.49.Final and 2.0.50.Final or later, including ${os.detected.classifier}. Check the linked wiki guidance for the intended behavior; done means the specified platform classifier is selected instead of only the full Uber jar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100