add ExtractVersionsAsProperties recipe#7655
Conversation
2340fd5 to
f9c1002
Compare
|
@timtebeek is the build failure caused by my change? I increased temporarly log verbosity and I see this error: I also get locally HTTP 429 from Maven Central repo but my tests are green. |
|
Hi thanks; no that's new unfortunately, unrelated to your changes. It seems like they're setting limits on calls to Maven Central, and we added an in between cache that doesn't work well on forks just yet. Working out the details still, but flying home from Code Remix Summit first. :) Thanks for the work here! Seems like a neat addition for our Maven best practices as well. Did you already run it there with success? |
4e82054 to
46d5426
Compare
I tried on AssertJ project with changes been done correctly: and build successful after changes. There is a small improvement but I will do it on a further PR - move duplicate properties into root pom.xml. |
|
@timtebeek in relation to "I've used the IntelliJ IDEA auto-formatter on affected files", I recall that I saw somewhere that Eclipse formatter plugin must be used, but I don't find this reference or how to set up it correctly. |
|
hey thanks no the default IntelliJ formatter is what we all use. Still hoping to get to your PR, but it's been awfully good weather over the weekend for hikes. ;) |
What's changed?
Add ExtractVersionsAsProperties recipe and tests.
What's your motivation?
Extract versions as properties in pom.xml.
Anything in particular you'd like reviewers to focus on?
I tried to make the code as clean as possible while still following project style.
Anyone you would like to review specifically?
Claude Code was used in small TDD iterations with manual review after each step.
Have you considered any alternatives or workarounds?
not aware of any
Any additional context
Checklist