Publish a BOM artifact to Maven Central

[brunoborges]

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.

[brunoborges]

/relevance-check

[github-actions]

Relevance Assessment: Still Relevant

• Summary: The request to publish a BOM (Bill of Materials) artifact has never been implemented. The feature remains valid and actionable against the current codebase.

• Evidence:

  • No bom/ module or BOM-related pom.xml exists anywhere in the repository.
  • No commits or PRs related to a BOM artifact have ever been created (git log --grep="bom" returns nothing; GitHub search for BOM PRs returns zero results).
  • The three modules proposed for inclusion in the BOM — gctoolkit-api, gctoolkit-parser, and gctoolkit-vertx — all still exist as active modules in the project (pom.xml, lines 87‑94).
  • The parent POM already defines these modules in (dependencyManagement) (pom.xml, lines 105‑140), which means creating a BOM would be straightforward.
  • The version referenced in the issue (2.0.4) is outdated — the project is now at 3.7.1-SNAPSHOT (latest release: gctoolkit-3.7.0). The milestone 2.0.5 attached to this issue was closed on 2023-02-28 without this being addressed.
  • No duplicate issues cover the same topic.

• Recommendation: ✅ Keep open — the feature has not been implemented and the request is still applicable. The referenced modules are all active, and the project's existing dependencyManagement section would make BOM creation straightforward. Consider updating the milestone assignment (currently set to the closed 2.0.5 milestone) and adjusting the example version numbers in the description to reflect the current 3.x versioning.

Generated by Relevance Check Agent for issue #169

[github-actions]

Relevance Assessment: Still Relevant

• Summary: The request to publish a BOM (Bill of Materials) artifact to Maven Central has never been implemented. The feature remains valid, actionable, and would simplify developer onboarding.

• Evidence:

  • No bom/ module, gctoolkit-bom artifact, or BOM-related pom.xml exists anywhere in the repository.
  • No commits mention "BOM" (git log --grep returns nothing), and no PRs have been opened for this feature.
  • The three modules proposed for inclusion — gctoolkit-api, gctoolkit-parser, and gctoolkit-vertx — all still exist as active modules in the parent pom.xml (lines 89–91).
  • The parent POM already defines these modules in (dependencyManagement) (lines 105–140), making BOM creation straightforward.
  • This is the only issue covering this topic — no duplicates found.
  • The version in the issue description (2.0.4) and the assigned milestone (2.0.5, closed 2023-02-28) are both outdated. The project is now at version 3.0.3-SNAPSHOT on main, with the latest release tag being gctoolkit-3.7.0.

• Recommendation: ✅ Keep open — the feature has not been implemented and remains applicable. Consider:

  • Removing or updating the stale 2.0.5 milestone assignment.
  • Updating the example version numbers in the issue body to reflect current 3.x versioning.

Generated by Relevance Check Agent for issue #169