malliaridis commented on PR #2809: URL: https://github.com/apache/solr/pull/2809#issuecomment-2546103156
> I would like to get some advice from the rest of the team: is this expected? The output is usually longer than expected, because right now the dependencies.gradle is adding constraints to all modules, including those that do not have any transitive dependency to one of the mentioned dependencies. This makes the output a bit verbose and confusing, which I don't like either. > What should be the procedure to solve this conflicting file? You usually are fine by looking into the starting line to find out which dependency and version has a conflict. Then, it should be sufficient to add that to the constraints file (dependencies.gradle). > Solving each conflicting line one by one proved not ideal And that is not expected to be necessary. [help/dependencies.txt](https://github.com/apache/solr/blob/44ea44d1fb07019e8bcd56c7a341301566d64deb/help/dependencies.txt) contains instructions on how to address these conflicts, but if you have any suggestion of improving this, please let us know. I am aware that this state is not optimal and often time-consuming. I am considering adding all our dependencies from the verison catalog as constraints by iterating through the list. That way we have likely less conflict occurences, but I am not sure how the performance during gradle builds is impacted and if this may introduce other issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
