clearlydefined / clearlydefined/service
How do we represent a Maven classifier in ClearlyDefined coordinates?
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Maven GAVs have an optional part that allows the specification of a classifier.
e.g.,
> Executing on a build that uses OpenJFX:
>
> mvn dependency:list
>
> on Linux:
>
> org.openjfx:javafx-base:jar:14:compile
> org.openjfx:javafx-base:jar:**linux**:14:compile
>
> on Windows:
>
> org.openjfx:javafx-base:jar:14:compile
> org.openjfx:javafx-base:jar:**win**:14:compile
>
In all cases the groupid, artifactid, and version are "org.openjfx", "javafx-base", and "14". Taking these dependencies from Maven Central, the ClearlyDefined Id is the same in all cases:
> maven/mavencentral/org.openjfx/javafx-base/14
It strikes me that the classifier should be part of the name in a ClearlyDefined ID, but I can't find any reference to a convention that would make this consistent.
How should this be handled?
Contributor guide
Research direction
Start by comparing Maven GAVs, including classifiers such as linux and win, with the current ClearlyDefined ID convention and Maven Central coordinates. Determine whether classifiers require distinct coordinates and document or implement one consistent representation; done means the handling is unambiguous for platform-specific artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100