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
Support deploying JARs and POMs to Maven compatible repositories #953
Comments
notice that |
What do you mean with "not useful"? AFAICT there's a checksum rule that triggers when there are no matching checksum files. |
no, not for |
Oh, oh, So it's the gradle plugin I'm using that calculates checksums for signature files ... well what a surprise there 😏 Thus, I only have to calculate checksums for JARs & POMs, but not for signatures, right? |
Also support:
|
Released in v1.3.0 -> https://github.com/jreleaser/jreleaser/releases/tag/v1.3.0 |
Sonatype Nexus2 powers Maven Central for the time being. Publishing artifacts to Maven Central has been requested since the early days.
JReleaser may need a new wrokflow step:
deploy
.JARs & POMs should be "staged" using the build tool of choice that is, files should be placed at a local directory using the default layout expected by Nexus. For example
Additionally, JReleaser may perform the following tasks before deploying takes place:
-sources
&-javadoc
JARs are availablesha256
andsha512
checksumsThe text was updated successfully, but these errors were encountered: