Oh I think I might see it now, there is a "source pom" and generated ones

some tools can work from the generated pom.xml, so in some cases you might find it useful to check in the generated pom.xml (and in that case, I would name the generated one something like template-pom.xml)

Ok, good idea, thank you

In all my projects, I used to keep the src-pom checked in (in a subfolder but it could easily have been just a different name) and then just generate into target as part of the jar build. Most of my projects had a src-pom that was generated by clj-new or deps-new which has more sections in it than the basic tools.deps (or tools.build) generated pom.xml. Yesterday, with the release of tools.build 0.9.6 and the addition of the pom-data option, I got rid of the src-pom and checked in file and switched to providing all that extra information in build.clj via pom-data. You can look at HoneySQL or next.jdbc for examples.

@U04V70XH6 cool! I'm gonna take a peek at your changes. I only had what I was calling "anemic" pom.xml files checked into git because tools.build couldn't fill in some blanks for me.

https://github.com/seancorfield/next-jdbc/blob/develop/build.clj#L35-L60 is how I'm doing it now (I can post a link now I'm not just on my phone). Here's the commit where I deleted the old template/pom.xml and switch to that Hiccup-style data: https://github.com/seancorfield/next-jdbc/commit/35eb931877c337103aae6f7145c168b31b635696