-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix double deployment of unwanted plugin marker to Maven Central #187
base: main
Are you sure you want to change the base?
Conversation
Thanks for the contribution. Unfortunately some of your commits don't meet our standards. All commits must be signed and have author information set. The commits to review are:
See Signed Commits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, I'm no gradle expert, but I don't see why it would not work. ;)
@@ -183,5 +183,16 @@ jreleaser { | |||
} | |||
} | |||
|
|||
// Remove unwanted "scan" directory after publishing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is done "after publishing" would that mean the additional artifact would have been already uploaded to Central?
@@ -15,5 +15,5 @@ | |||
# | |||
|
|||
group=org.sonatype.gradle.plugins | |||
version=3.0.0-SNAPSHOT | |||
version=3.1.0-SNAPSHOT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no change in the plugin code, if the intention is to test this releasing a new version then it's better just to increment the patch number:
version=3.1.0-SNAPSHOT | |
version=3.0.1-SNAPSHOT |
Fixes extra deployment to Maven Central of unwanted plugin marker
Fixes issue #185