Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish to Maven Central repository #2

Merged
merged 36 commits into from
Nov 4, 2024

Conversation

dennisvang
Copy link
Collaborator

@dennisvang dennisvang commented Oct 25, 2024

This PR implements publication to the Maven Central repository (fixes #3):

  • changed groupId from com.github.fairdevkit to org.fairdatateam.rdf
  • changed package namespace (and corresponding paths) from com.github.fairdevkit to org.fairdatateam.rdf for consistency
  • separated build/test workflow from publication workflow
  • simplified and upgraded workflows
  • configured pom and workflows for publication to Maven Central Portal
  • bumped minor version to 0.2.0

QUESTIONS:

  • Actually the modified namespace is a breaking change, because dependent projects need to update their pom and imports. Given that the package has been in "production" use for some time, perhaps it would be better to bump to 1.0.0?

TODO:

  • enable issue tracking in upstream
  • configure upstream repository secrets (GPG key, central portal access token)

and adapt worflow with
  - explicit temurin distribution
  - java version matrix (temurin LTS versions)
  - latest versions of actions (v4)
and rename ci.yml to maven-ci.yml for consistency
temporarily using dennisvang account for dev convenience
using `revision` property, as defined in [maven docs][1]

[1]: https://maven.apache.org/maven-ci-friendly.html#multi-module-setup
required when using project versioning based on `revision` property, as in [CI friendly versions][1]

[1]: https://maven.apache.org/maven-ci-friendly.html#install-deploy
this is a test, because docs are conflicting w.r.t. the need for --pinentry-mode etc.
as required for publication to maven central
trying to debug the maven central validation process
because this may complicate publication
the changes are backward incompatible, but we are still in major 0, so we only increment minor
… remove version modifier

Use hardcoded urls because variables are not expanded during publication, resulting in broken urls in package metadata on maven central.
Signing is only required in maven-publish. Moreover, it causes the maven-ci workflow to fail if triggered by PR from fork, because I does not have access to github secrets.
@dennisvang dennisvang marked this pull request as ready for review October 28, 2024 16:45
@dennisvang
Copy link
Collaborator Author

Please squash merge.

@luizbonino luizbonino merged commit 9ee2669 into FAIRDataTeam:develop Nov 4, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Publish to Github Packages or Maven Central repository
2 participants