-
Notifications
You must be signed in to change notification settings - Fork 41
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
Update publish-plugin to published signed plugin artifacts #295
base: master
Are you sure you want to change the base?
Conversation
I tried to test it by changing plugin id and publishing it from my personal account. Obviously, verification on the portal side failed and the submission was rejected, but looking into Gradle's logs it seems like @adam-enko, @Tapchicoma maybe you guys know a better testing approach? |
Personally I test publishing by adding a local directory and manually verifying the files. |
Looking at the PR, imho it'd be better to update kotlinx team infra plugin to avoid such workarounds. The last time I looked at the infra plugin it used a lot of non-idiomatic practices that could be refactored to avoid these issues. Is updating the infra plugin feasible? |
I considered that option, but there's only a few projects still using the plugin and I though it would be easier to update one of them to exclude the duplicated artifact instead of updating all other projects to include it explicitly.
It makes sense to do all that at some point and then get rid of the workaround I'm adding here. |
Apparently, signature files are always published to a local repo, no matter what version of publish plugin I'm using :/ |
I just saw another user posted in the Gradle Slack with the same problem. Possibly there's an issue with the Plugin Portal? ![]() https://gradle-community.slack.com/archives/CA745PZHN/p1741602255845399 (archive) |
I'll check it, thanks for pointing to it! |
Updated infra and published plugins to unlock signed plugin artifacts publication.
Closes #115