Where to put Version in the URISyntax
This page does not deal with the VersionSyntax, only the position (or positions) in the URI/URL (See /URISyntax).
Version in Directory, optional in Artifact Name as listed in /URISyntax, has enough of a consensus to move forward.
Proposals
(Vote by placing your name by a proposal. You can change your vote.)
Version in Directory, optional in Artifact Name
Narrative
Each Version has it's own directory as part of the URI. Version is optional in the artifact name.
Pros
Easier parsingAdamJack
- All artifacts for a given version in one place.
- Easy to navigate.
- Easy to archive artifacts for one project version.
- Optional version in artifact name is compatible with existing maven and ASF dist usage.
Cons
- Leads to data duplication, if the version is also specified in the artifact name.
Votes
TimAnderson (non-binding)
Version in Artifact Name Only
Narrative
Every Artifact name must include a version part. There is not a directory for each version.
Pros
- Artifact is self descriptive even after download
Cons
- One big directory with many artifacts.
- Hard to navigate.
- Hard to archive artifacts for one project version.
- Not compatible with existing maven and ASF dist usage.
- Artifact naming requirements for non-java based repository users not known.
Votes
Version in Directory and Artifact Name
Narative
The URL contains both the version directory and the version in the artifact name.
Pros
- Easy search
- Artifact is self descriptive even after download
Cons
- Not compatible with existing maven and ASF dist usage.
- Artifact naming requirements for non-java based repository users not known.
Votes