The changes.txt file confuses me a lot and I would love to see some improvements there. It is not clear to me at the moment of the PR creation / merge which version will be next to add the change entry to. Using a tool like the one Jan proposed makes sense to me and would likely solve the issues I see.
Alessandro, you mentioned error-prone as an issue, I believe you are talking about google error-prone. I wanted to enable more rules step by step to avoid potential issues (see for example https://github.com/apache/solr/pull/2881). I was not aware that this may be an issue. Could you please elaborate on this? Allow me to add the dependency resolution process as another issue, that I have made worse in the main branch. I still believe in the switch to the gradle version catalogs, but I think it should be easier and more straight-forward to resolve dependency conflicts. I am still working on that topic and have already a few improvements in a draft that I would like to add once there is a working version (see https://github.com/apache/solr/pull/2915). If you have any input on that please share it. Best, Christos --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
