Clojurians Log v2
clojars
I tried to run it on the repo cached on the server last night, but realized my recollection of how we build the maven index was wrong - we pull down the poms, not the jars for indexing :( However, I think we could: • pull down the jars once and index those, then store the index in s3 • index new jars as they are deployed, then merge with the existing index This should work since existing releases are immutable. We could also store the index as many timestamped files - that would allow clients to be able to cache the index, pulling down new files and merging them. I suspect the full index file will be pretty large.
yeah, those are good ideas
I like the second idea
then we can just pull only the latest files
Good deal. We should probably open an issue at https://github.com/clojars/clojars-web/issues/new/choose and continue this discussion there
Thanks!
Hi all, sorry to burst in with a problem, but I'm trying to push a repo and it's not being accepted. Is xn--lgc/pure-conditioning an invalid name? The error I'm getting is
Could not transfer artifact xn--lgc:pure-conditioning:jar:0.1.0 from/to clojars (<https://repo.clojars.org/>): Failed to transfer file <https://repo.clojars.org/xn--lgc/pure-conditioning/0.1.0/pure-conditioning-0.1.0.jar> with status code 401The name is because it's related to my domain: http://www.xn--lgc.com/pure-conditioning
It is being rejected because you are deploying with a password instead of a deploy token. See https://github.com/clojars/clojars-web/wiki/Deploy-Tokens. We used to be able to tell you that when the deploy failed, but can no longer due to https://github.com/clojars/clojars-web/issues/774
Also, if this is a new group you are creating, I'd recommend using com.xn--lgc instead. We're going to soon move to requiring new groups to be reverse-domain based and verified, so doing so now would put you ahead of the game.
Ok, thanks very much. I made a token and was surprised when lein deploy didn't ask me for it.