[
https://issues.apache.org/jira/browse/SOLR-18397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107508#comment-18107508
]
Chris M. Hostetter commented on SOLR-18397:
-------------------------------------------
Oh .. interesting, ok well since that only exists in
{{solr/modules/ltr/gradle.lockfile}} which has no other (incorrect) "Copy"
configurations, the simplest thing is probably...
{noformat}
find -name gradle.lockfile | xargs perl -i -ple 's/(,?[^,]+Copy)//g'
git restore solr/modules/ltr/gradle.lockfile
git add -A{noformat}
that should work fairly cleanly on both branches even if the incorrect "Copy"
configurations differ between the branches.
> Manually cleanup '*Copy' configuration names in grade.lockfiles
> ---------------------------------------------------------------
>
> Key: SOLR-18397
> URL: https://issues.apache.org/jira/browse/SOLR-18397
> Project: Solr
> Issue Type: Task
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-18397.patch
>
>
> 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.
>
> SOLR-18396 exists to try and fix solr-bot to stop doing this, while this Jira
> exists to attempt a cleanup of the existing lockfiles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
