tools-build

seancorfield 2025-10-27T18:17:07.711409Z

I wonder if there have been any thoughts on a suitable approach for https://clojure.atlassian.net/browse/TBUILD-41 (this is the Ask: https://ask.clojure.org/index.php/13802/ignore-pom-default-for-clojure-tools-build-api-write-exists ). There doesn't seem to be any existing similar precedent, so either :src-pom :none or :src-pom :ignore seem to be reasonable approaches here? Would there be interest in a PR^H^Hpatch for this?

Alex Miller (Clojure team) 2025-10-27T18:21:22.836909Z

I think I started looking at it and couldn't decide what approach to take

Alex Miller (Clojure team) 2025-10-27T18:25:28.269619Z

:src-pom :none seems fine, happy to look at a patch

Alex Miller (Clojure team) 2025-10-27T18:27:00.877029Z

would be looking for update to docstring, code, and added test in test-pom

seancorfield 2025-10-27T18:28:02.143739Z

Yup, NP. I may take a run at it this week if I need a break from the horrors that are React Native and IAP 🙂

👍 1
seancorfield 2025-10-27T19:08:41.450059Z

I decided I needed a break from those horrors... how does https://github.com/clojure/tools.build/compare/master...seancorfield:tools.build:master look? I noticed a missing not in the API doc about :pom-data, and the existing note about when :pom-data is used wasn't entirely accurate, so I updated both of those too. If this looks reasonable, I'll make a .patch and attach it to the JIRA ticket.

Alex Miller (Clojure team) 2025-10-27T19:13:49.043359Z

I think that absence of "not" was correct?

seancorfield 2025-10-27T19:14:42.986419Z

Oh, because it refers to the existing source pom.xml, not :pom-data! Duh! Will fix.

Alex Miller (Clojure team) 2025-10-27T19:15:35.791309Z

don't modify the docs dir, those are generated

seancorfield 2025-10-27T19:16:06.176909Z

Ah, OK, I misunderstood your note about updating docs, sorry.

Alex Miller (Clojure team) 2025-10-27T19:17:40.980189Z

I meant in the api docstring, sorry if that wasn't clear

Alex Miller (Clojure team) 2025-10-27T19:17:58.140259Z

rather than add the p4 testdata, you could just reuse the existing p2 one

seancorfield 2025-10-27T19:18:25.011059Z

Well, I needed to verify the source pom.xml data was actually used -- and p2 didn't have scm

Alex Miller (Clojure team) 2025-10-27T19:19:07.934239Z

ok

seancorfield 2025-10-27T19:19:31.783489Z

The new test is essentially the test for p2 + source scm, to ensure that if the source is ignored, you get no scm.

seancorfield 2025-10-27T19:20:11.142229Z

There are no tests currently that verify existing pom.xml info is preserved 🙂

seancorfield 2025-10-27T19:38:02.147109Z

Patch created and attached to the ticket.

👍 1