Replies: 3 comments 1 reply
-
Also:
And finally in my Jenkins job I've decided to do |
Beta Was this translation helpful? Give feedback.
-
If both moduleA and moduleB belong to the same multi-project build and if they are to be released in tandem then I suggest moving the jreleaser configuration to the root, configure staged publication to a shared directory, and run the jreleaser tasks from the root alone. |
Beta Was this translation helpful? Give feedback.
-
The issue here would be that these are not the only modules in this project. Is there a way to run the tasks from the root, but specify which specific modules should be actually deployed? |
Beta Was this translation helpful? Give feedback.
-
I have a setup which is meant to release 2 artifacts in maven central. They are gradle modules, sitting in the same root directory (root/moduleA and root/moduleB). Module A is also an implementation dependency od module B.
I basically call:
The first deploy, for the moduleA, goes ok, everything is correctly staged in ossrh. However the second deployment, on the jreleaserSign stage, throws an exception:
Even if I run only the deployment for moduleB, without the deployment for moduleA - it also fails in the same way.
I tried running it without the
clean
part - it also failed.I also tried manually creating the directory, but still - no success:
I'm a bit out of ideas, do you have any idea what could still be wrong here?
My setup:
Java 11, Gradle 8.5, JReleaser plugin 1.11.0
Beta Was this translation helpful? Give feedback.
All reactions