-
Notifications
You must be signed in to change notification settings - Fork 148
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
Broken release on Maven Central #481
Comments
@wiget thx for pointing out, gonna check it out as soon as possible! |
I'm trying to figure out the problem, the faster way will be to release next (snapshot) version, @wiget will you check it?:) |
Sure, I can test. Just let me know version number. |
@wiget i've released v1.13.11 - please check it out - this project is not ready to use anykind of gradle plugin snapshots ;( |
@bgalek comparing your last commit to Gradle documentation I think Something like this
|
I've seen this, but during the local maven publication it looked like it didn't make any difference - if the latest version still has problems I'll try that. We need to move from build.gradle to kts so this kind of things will be type checked. |
@wiget did you manage to test latest version? :) |
If you mean v1.13.11, then yes. I used this Gradle project to test it: https://github.com/wiget/axion-test Running
As you see metadata file for gradle plugin is missing on Maven Central. |
I used |
@wiget I'll double checked jars published to maven local after moving |
released v1.13.12, |
From my testing it look like Here is how local maven repository looks after
and here with
|
and with setAutomatedPublishing(true) maven publish fails saying that there are two artifacts that ale colliding ;/ |
@wiget https://github.com/allegro/axion-release-plugin/pull/486/files we can try it, as long as maven artifact won't be published (was the problem last time) I can always "withdraw" gradle portal publication |
@wiget https://github.com/allegro/axion-release-plugin/runs/6757276720?check_suite_focus=true I'm trying to distinguish artifact from plugin from the actual jars but as you see it's tricky ;( |
@wiget I've also updated badge to see any differences with maven/gradle fast |
#487 should help for colliding artifacts |
@wiget thx, this could also be the way to go - as for now, the issue is resolved with v1.13.13 right? |
Nope.
plugin marker is missing. |
@wiget it's 404 for me, maven central sync takes some time |
After successful publication I will expect two directories here: https://repo1.maven.org/maven2/pl/allegro/tech/build/
|
@wiget i can't see older versions of |
Correct. |
I see, that was the missing puzzle!
as I've already created a lot of havoc with those dummy versions, I'll create another one with your changes |
v1.13.14 released, it will take a while to sync maven central if you do not use sonatype as a taget |
Works with following settings:
Will re-check against Maven Central in few hours. |
Works with Maven Central too. Thank you. |
Jar for version 1.13.10 released to Maven Central is broken in some way.
Jar from Gradle Plugins works without problem.
https://plugins.gradle.org/m2/pl/allegro/tech/build/axion-release-plugin/1.13.10/axion-release-plugin-1.13.10.jar has md5 hash
fb245869dbbf1ebfd0eb25fe83c128fa
but https://repo1.maven.org/maven2/pl/allegro/tech/build/axion-release-plugin/1.13.10/axion-release-plugin-1.13.10.jar has md5 hash
d39481b8f5dc729250d2086ae313ba72
The text was updated successfully, but these errors were encountered: