This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-28
Channels
- # adventofcode (6)
- # beginners (61)
- # boot (1)
- # chestnut (1)
- # cider (18)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (176)
- # clojure-android (8)
- # clojure-germany (12)
- # clojure-russia (4)
- # clojure-spec (7)
- # clojure-uk (5)
- # clojurescript (28)
- # css (10)
- # cursive (36)
- # datomic (7)
- # devcards (1)
- # docs (8)
- # emacs (17)
- # fulcro (29)
- # hoplon (28)
- # lein-figwheel (3)
- # leiningen (37)
- # lumo (1)
- # off-topic (54)
- # om (6)
- # re-frame (2)
- # reitit (7)
- # ring-swagger (23)
- # shadow-cljs (115)
- # sql (10)
- # uncomplicate (1)
- # unrepl (24)
It’s very very unlikely we’re going to remove unofficial JARs from Clojars as that would break people builds. I think we could do a better job of highlighting shadowing, and possibly deprecating artifacts that are clearly unofficial
But the golden rule of Clojars is “don’t break the build” so any solutions will need to keep that in mind
I like the idea of being able to communicate a new canonical repo through tooling too
I suspect that a visible "caution" on the http://clojars.org/postgresql/postgresql page that the group ID shadows Maven Central (perhaps with a link to http://search.maven.org with that group ID) would have been enough to prevent @jgh from hours of pain there @danielcompton
Seems sensible. The set of repos is small enough to do it manually
maybe lein ancient
and lein deps :tree
could be extended to recognize warnable artifacts, and add eg. colorized output or explicit warnings
As some authors deliberately publish to both like cemerick and tcrawley
Yeah truth be told it doesn’t need to be a whole lot, just a clue that what you think you’re doing may not be what’s actually happening.
Hi! Is there a doc for what the s3p://
URL is?
For context: I'm using [s3-wagon-private "1.3.1"]
. I just hit an issue where a project.clj had s3://
and not s3p://
. Using s3p://
works. Curiously, however, I cannot find any docs on it, in projects, on AWS, or via Google.
It’s a custom wagon protocol
Plugins register support for different protocols. S3-wagon-private adds s3p
There’s probably a few that register S3
Ah, gotcha. That makes sense. I've seen it in a few S3 plugin projects, so was curious whether there's a common meaning for it. It appears to mean "private S3 bucket." That it's a custom protocol, not AWS, clarifies.
another victim to the postgresql clojars repo in #beginners … the body count continues to rise 😉
@jgh can you post any sites that reference the Clojars version on your issue and I’ll try and contact them
I opened this issue against one such project https://github.com/enyert/liberator-service/issues/1
Yep, but keep in mind s3 is also not a built in protocol either
They’re all extensions, the s3 one happens to look like an AWS s3 resource link but it’s not “official” in Maven
regarding artifact discovery and making people use the right version, maybe it would help to have a usable version of lein search
that doesn’t download the entire list of every version of every artifact available
right now it’s kind of unwieldy so even people that discover it don’t find it especially usable
I opened this issue against one such project https://github.com/enyert/liberator-service/issues/1
@noisesmith I think lein 2.8.0 has that feature now
oh, cool
It uses the api for search rather than the index
haha wow haven’t tried this in a while
$ lein search postgres
Searching central ...
[net.piotrturski.testegration/postgres "0.0.2-beta"]
[net.piotrturski.integrationjtest/postgres "0.0.1-beta"]
[com.cohesiveintegrations.ddf/postgres "1.3.1"]
[net.sf.squirrel-sql.plugins/postgres "3.5.0"]
[org.cloudhoist/postgres "0.7.0-beta.2"]
[org.umlg/sqlg-postgres-parent "1.4.1"]
[com.github.cafapi/java-postgres-container "1.13.0-35"]
[com.cohesiveintegrations.ddf.postgres/distribution "1.3.0"]
[com.cohesiveintegrations.ddf.postgres/source "1.3.0"]
[com.cohesiveintegrations.ddf.postgres/postgres-app "1.3.1"]
Searching clojars ...
org.xml.sax.SAXParseException: The value of attribute "description" associated w
ith an element type "result" must not contain the '<' character.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseEx
ception (ErrorHandlerWrapper.java:203)
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError (Erro
rHandlerWrapper.java:177)
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError (XMLErr
orReporter.java:400)
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError (XMLErr
orReporter.java:327)
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError (XMLScan
ner.java:1437)
wonder if that’s a leiningen bug or a clojars bug?
also that seems like a garbage result set from central?
I asked about this in #leiningen on freenode, if I don’t get a good response I’ll open a ticket I think
follow up: it’s a bug in cljars code
follow up follow up: it’s fixed
the quality of the results is still low though
@jgh btw we are discussing these issues right now on #leiningen on freenode
(as mentioned in topic message for this channel)