clj-commons

slipset 2020-01-08T19:33:42.000500Z

eew. pomegranate is a maven project.

seancorfield 2020-01-08T19:43:59.001200Z

Yeah, I wasn't sure what to do once I'd eliminated the "obvious" build problems (like trying to use Oracle JDK 7 at this point).

slipset 2020-01-08T20:53:33.001600Z

There is also the problem with artifact deployment.

slipset 2020-01-08T20:54:06.002300Z

I tried to contact @cemerick about this, but haven’t got an answer from him yet.

2020-01-08T20:54:10.002500Z

@cemerick has joined the channel

slipset 2020-01-08T20:54:46.003200Z

When I contacted him, I assumed that pomegranate was published to clojars, but I see now that it’s published to maven central.

slipset 2020-01-08T20:55:43.004400Z

Knowing that it’s hard/impossible to transfer ownership of single artifacts in clojars, I’d imagine it’s as hard in maven central.

slipset 2020-01-08T20:56:45.005100Z

I see that for nrepl (another project that originated with @cemerick), the coordinates changed.

seancorfield 2020-01-08T20:58:01.005900Z

I think it would be fine for future Pomegranate releases to be clj-commons/pomegranate on Clojars. As long as @cemerick is cool with that.

seancorfield 2020-01-08T20:58:55.006800Z

It's clear that folks can deal with a library changing its coordinates on a version change as long as it's communicated well.