-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Problem with Clojars dropping / ignoring some artifacts? #532
Comments
This is indeed related to #226 and #505, and is the same root cause as #515. We currently use the upload of
I have a fix in mind that I will try to get implemented today - sorry for the trouble. |
Maven will upload *any* classified artifact after uploading maven-metadata.xml. We use maven-metadata.xml as a trigger to know when to finalize the deploy, moving the contents to the actual repo and to cloudfiles. Before this change, we essentially ignored any files that came in after the finalization. Now, any files that come in after finalization go straight to the actual repo and to cloudfiles. This means that deployments with classified artifacts is no longer atomic - the primary artifact, pom, and maven-metadata.xml will be consistent, but any classified artifacts won't be part of that atomic unit. This commit also switches us from clj-http-lite to clj-http for testing, since we need cookie support to properly test this change, since we need to control the order of deployment, so can't use aether.
I have a fix for this on master - I need to schedule a maintenance window to deploy it, since there are other changes in the pipe that require db migration. I'll try to make that happen early next week. |
Awesome thanks @tobias ! Will save me a lot of time vs. having to manually copy snapshots around! |
@mikera - I tried to deploy this fix earlier this week, but had to roll it back due to unrelated issues. I'm fixing those now, and hope to try again early next week. |
@mikera - this should now be fixed. I deployed a fork of I'm closing this, but feel free to reopen if you see any issues. |
Hi,
I've been hitting problems releasing core.matrix to Clojars - it seems to be dropping the test jars that previously uploaded fine. Compare:
https://clojars.org/repo/net/mikera/core.matrix/0.52.1/
With the older release:
https://clojars.org/repo/net/mikera/core.matrix/0.50.0/
As you can see, the older release included a lot more artifacts. I'm pretty sure the artifacts all got uploaded as reported by Maven:
Uploaded: https://clojars.org/repo/net/mikera/core.matrix/0.52.1/core.matrix-0.52.1-tests.jar (63 KB at 28.8 KB/sec)
So it appears that the Artifacts are now being dropped by Clojars at some point.
The text was updated successfully, but these errors were encountered: