clj-commons

slipset 2020-01-09T06:26:43.008700Z

Got this from Chaz: > I think it's probably best if the new repo/artifact goes under its own group with new coordinates

seancorfield 2020-01-09T06:30:14.009100Z

That's great! Thanks @slipset

slipset 2020-01-09T07:07:47.010400Z

I haven't studied the pom.xml file in detail, but it might be worth rewriting it to either deps.edn or project.clj?

slipset 2020-01-09T07:08:49.011Z

Which leads to the question wether we should bother trying to standardize on one build-tool chain?

slipset 2020-01-09T07:09:37.012Z

I'm favourable to that as it makes it easier to do maintenance across multiple projects (which is why I tend to change from whatever to circle-ci).

slipset 2020-01-09T07:11:32.013400Z

One benefit of using Maven (or rather a checked in pom.xml) is that the lib is consumable by deps.edn as a git depenency, right?

seancorfield 2020-01-09T07:12:10.014Z

deps.edn and/or pom.xml makes sense. project.clj does not.

slipset 2020-01-09T07:13:40.014300Z

Agreed.

slipset 2020-01-09T07:15:00.014900Z

And I believe you have a certain grasp on deps.edn stuff, so you might be able to help out there 🙂

slipset 2020-01-09T07:16:04.015400Z

the pom seems extremely simple.

seancorfield 2020-01-09T07:17:19.016200Z

Given a deps.edn file, clojure -Spom produces a pom.xml file that needs only minimal changes.

seancorfield 2020-01-09T07:17:48.016600Z

(group, artifact, version, generally)

slipset 2020-01-09T07:32:45.017300Z

I've added a barebones deps.edn file.

👍 2