We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The packages is currently only published on Github under the private package repository. To make a release to Maven Central here are the links: https://docs.github.com/en/actions/publishing-packages/publishing-java-packages-with-maven#publishing-packages-to-the-maven-central-repository https://dzone.com/articles/how-to-publish-artifacts-to-maven-central
The text was updated successfully, but these errors were encountered:
Before releasing the package, we need the license (according to https://dzone.com/articles/how-to-publish-artifacts-to-maven-central). (cf. Issue Add licenses to the source files #2 and PR Add license #8)
Also, we should change the group ID in the POM to de.maibornwolff (our convention according to https://intranet.maibornwolff.de/display/MWeaMethodik/Technical+stuff)
Sorry, something went wrong.
No branches or pull requests
The packages is currently only published on Github under the private package repository.
To make a release to Maven Central here are the links:
https://docs.github.com/en/actions/publishing-packages/publishing-java-packages-with-maven#publishing-packages-to-the-maven-central-repository
https://dzone.com/articles/how-to-publish-artifacts-to-maven-central
The text was updated successfully, but these errors were encountered: