malliaridis closed pull request #2915: Optimize dependency resolution via
platform module
URL: https://github.com/apache/solr/pull/2915
--
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 c
malliaridis commented on PR #2915:
URL: https://github.com/apache/solr/pull/2915#issuecomment-2602716704
Closing this in favor to https://github.com/apache/solr/pull/2925
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
dsmiley commented on PR #2915:
URL: https://github.com/apache/solr/pull/2915#issuecomment-2564228811
Ah; thanks for making the important distinction between constraints and
dependencies. Your Gradle knowledge is impressive!
--
This is an automated message from the Apache Git Service.
To
malliaridis commented on PR #2915:
URL: https://github.com/apache/solr/pull/2915#issuecomment-2560092738
> SolrJ depends on "api" module too; so does this mean we unwittingly add
dependencies for SolrJ users which they previously didn't have?
We have to distinguish between constraints
malliaridis opened a new pull request, #2915:
URL: https://github.com/apache/solr/pull/2915
# Description
After the upgrade to version catalogs there were changes made in the way our
project resolves the dependencies. The new "flow introduced has proven to be
quite confusing and prob
