You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2022/12/09 09:36:00 UTC
[jira] [Updated] (IGNITE-18359) Fix build after merging IGNITE-18117
[ https://issues.apache.org/jira/browse/IGNITE-18359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mirza Aliev updated IGNITE-18359:
---------------------------------
Summary: Fix build after merging IGNITE-18117 (was: Fix build after merging https://issues.apache.org/jira/browse/IGNITE-18117)
> Fix build after merging IGNITE-18117
> ------------------------------------
>
> Key: IGNITE-18359
> URL: https://issues.apache.org/jira/browse/IGNITE-18359
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After merging https://issues.apache.org/jira/browse/IGNITE-18117 there was some problems because of recent changes in the main branch. The conflict was because this code
> {code:java}
> distributionZoneManager = new DistributionZoneManager(zonesConfiguration, metaStorageMgr, cmgMgr);
> {code}
> was initialised twice.
> This's happened because in both tickets this line of code was moved, so after merged this line was duplicated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)