[
https://issues.apache.org/jira/browse/SOLR-18396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106804#comment-18106804
]
Jan Høydahl edited comment on SOLR-18396 at 8/22/26 12:13 AM:
--------------------------------------------------------------
Yes, I've been fighting this flip-flopping lockfiles more than once and the
renovate "fix" is on me. See dev@ answer and a draft PR made by AI that tries
to clean up not only renovate but the gradle build to stop polluting Copy
things into lockfiles: https://github.com/apache/solr/pull/4794
was (Author: janhoy):
Yes, I've been fighting this flip-flopping lockfiles more than once and the
renovate "fix" is on me. See dev@ answer and a draft PR made by AI that tries
to clean up not only renovate but the gradle build to stop polluting Copy
things into lockfiles:
https://github.com/apache/solr/pull/4794https://github.com/apache/solr/pull/4794
> Figure out why Solr-Bot is adding '*Copy' configuration names to
> grade.lockfiles
> --------------------------------------------------------------------------------
>
> Key: SOLR-18396
> URL: https://issues.apache.org/jira/browse/SOLR-18396
> Project: Solr
> Issue Type: Task
> Reporter: Chris M. Hostetter
> Priority: Major
>
> Solr-Bot seems to have started adding a bunch of {{fooBarCopy}}
> configuration names to many of our {{gradle.lockfile}} files anytime it
> needed to modify a {{fooBar}} configuration.
> this is causing problems when attempting to update lucene (and presumably
> other dependencies updated by hand?) because gradle detects version
> constraint conflicts that can't be resolved.
> presumably we should fix Solr-Bot to stop doing this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
