eew. pomegranate is a maven project.
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).
There is also the problem with artifact deployment.
I tried to contact @cemerick about this, but haven’t got an answer from him yet.
@cemerick has joined the channel
When I contacted him, I assumed that pomegranate was published to clojars, but I see now that it’s published to maven central.
Knowing that it’s hard/impossible to transfer ownership of single artifacts in clojars, I’d imagine it’s as hard in maven central.
I see that for nrepl (another project that originated with @cemerick), the coordinates changed.
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.
It's clear that folks can deal with a library changing its coordinates on a version change as long as it's communicated well.