-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Issue with postReleaseGoals parameter #144
Comments
Which information exactly?
Have you set |
Yes I do but i can´t see the gpg maven plugin configuration. I put a log file of release and deploy proccess. You can reproduce the error using the plugin gpg-maven-plugin and execute gpg: sign. |
Have you tried to set Try also adding |
@limkinZero Have you resolved this? |
Yes but I had to do in two steps. I can't use the post release task. I don't know why the process doesn't take maven got parameters. |
Could you please describe exactly how you resolved this? |
I did in two maven steps changing to master branch. - mvn $MAVEN_CLI_OPTS -B gitflow:release -DskipTests=true
- git checkout master
- mvn $MAVEN_CLI_OPTS deploy -DperformRelease=true |
I have a similar issue - I am using custom settings - EDIT: |
Hi @aleksandr-m,
I am using the parameter to deploy the generation of the release within my gitlab-ci
mvn -B gitflow:release -DpostReleaseGoals=deploy -DskipTests=true
and I'm getting errors when signing my artifacts. The fact is that I use the plugin
maven-gpg-plugin (v1.6)
and getting the following error:If instead of doing the deploy as a subphase of the release I execute it by itself as mvn deploy, the process ends correctly.
I think the plugin is not passing all the information to the third-party plugins that are running in the phase. I have set the DEBUG mode but the plugin does not get the detailed information of the configuration of the maven-gpg-plugin. I think this could be another bug.
The text was updated successfully, but these errors were encountered: