microsoft / microsoft/gctoolkit
Publish a BOM artifact to Maven Central
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
By publishing a BOM, developers would only need to add a single dependency to their projects, simplifying consumption and onboarding experience for developers who just want to use GCToolkit in their projects.
Proposal
Apache Maven:
<dependency>
<groupId>com.microsoft.gctoolkit</groupId>
<artifactId>gctoolkit-bom</artifactId>
<version>2.0.4</version>
</dependency>
Gradle:
implementation 'com.microsoft.gctoolkit:gctoolkit-bom:2.0.4'
This artifacts would depend on:
- gctoolkit-api
- gctoolkit-parser
- gctoolkit-vertx
Experienced developers would still be able, in the future, to consume only the API and/or the Parser, if so, they choose.
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 by locating the project's Maven build and module declarations, then inspect how existing artifacts are published to Maven Central. Define the BOM artifact with gctoolkit-api, gctoolkit-parser, and gctoolkit-vertx as dependencies, and verify that the Maven and Gradle coordinates in the issue resolve to the published artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100