Validate pom + components properties
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 131
- Forks
- 10
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 6
Description
This is a follow up from @IgnatBeresnev excellent talk at KotlinConf. We could enforce that properties have meaningfull values. One example I have in mind is using a SPDX license id for license name.
We could also validate the components (make sure everything has sources, signatures, extensions, etc...)
- SPDX license identifiers
- valid
groupId - valid
artifactId - Sonatype requirements
- all files must have an extension
- snapshots must end with
-SNAPSHOT - releases must not end with
-SNAPSHOT - GPG keys have been uploaded to a central server (from https://central.sonatype.org/publish/requirements/gpg/#distributing-your-public-key)
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
Start by locating the pom and component validation entry points, then read the linked Sonatype publishing requirements and the checklist in this issue. Done means meaningful SPDX license identifiers, valid groupId and artifactId values, required component files and extensions, correct snapshot and release naming, and verifiable GPG key distribution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100