Thank you @seancorfield will test this morning 🙂
Yup works - but first had to align the scm tag to the same as the version, then update
works grand now 🙂
Cool. Yeah, if they're out of sync, it can't do much to sync them back up.
When I first implemented :sync-pom true
, if you specified :version
and had an existing pom.xml
, the call into t.d.a would update the <version>
field and then my own sync'ing code couldn't match <tag>
match (because the version field had already been changed).
So now, :version
(and :group-id
and :artifact-id
) are only passed to t.d.a's pom-sync'ing code when no pom.xml
exists.
(and in that case, there's no <tag>
)
YOu know, I did the obvious thing when I first tried it out yesterday, I did sync-pom without reading the documentation (and not having a pom.xml). It threw a NPE to the console. After reading the documentation, I added in the version, groupid etc., and it worked. However, do you think it might be worthwhile to catch that NPE (for dummies like me) and guide the user to add in a groupid, artifactid and version?
Probably a good idea. I could even trap it before calling into t.d.a and give a better message altogether.
That would be helpful 🙂 Something to ponder.
noice
I'll need to clean up the option verification stuff before I can implement that. The code needs a serious refactor. It's at the limit of what I can maintain in the main function right now.
you have a lot on your plate! this, honeysql, next.jdbc....
The sponsorship really helps... it means I can really justify working on OSS for whole days at a time instead of a few hours here and there.
Jay is happy for me to be doing "semi-work" instead of watching TV 🙂
🙂 Let me know if I can be of any assistance. Happy to spend a few hours testing things out if you need someone.
("work-work" is my day job, "play-work" is unpaid stuff I do on the computer, "semi-work" is the new term for "unpaid stuff I do" that I'm now actually getting paid for)
Thanks. You're a very proactive user of several of my projects and that is very valuable on its own because you actually provide feedback (both positive and negative) on how stuff actually works.
you're most welcome! 🙂
The next "big" piece of work is to break my current logjam on HoneySQL...