clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
eskos 2020-06-25T08:19:44.033200Z

Is it possible to attach custom project metadata to clojars publish? I’d want to tag versioning scheme, as it seems break versioning is gaining traction, and some people use date of release, while SemVer is what Maven natively just assumes, even though Maven’s versioning is way older than the SemVer spec. Reason for this is that using tools such as lein ancient would need this metadata to be able to work correctly, as it simply expects SemVer with Maven’s snapshot/qualified additions.

2020-06-25T18:36:28.033300Z

Where are you located geographically? We've had a few reports of this and I wonder if it is related to where a Fastly edge node is and therefore which s3 endpoint it is using.

2020-06-25T18:45:52.033500Z

There's no direct way to attach metadata since we are built on top of maven poms which aren't really extensible. A few options I've thought about for something like this are: • setting properties in the pom file - those are intended to be used to set system properties at runtime, but could be abused to store metadata • adding a optional metadata file that can be deployed alongside an artifact. It would use maven's classifier system, so wouldn't custom deployment machinery. It would require lein/whatever changes or plugins though