Hi Igniters, While fixing documentation code snippets compilation, I noticed something odd around the cloud IP finder extension.
IGNITE-17137 [0] moved ignite-cloud from the main Ignite repository to ignite-extensions: - apache/ignite#10079 removed modules/cloud - apache/ignite-extensions#157 added modules/cloud-ext The docs now list ignite-cloud-ext as an available extension for TcpDiscoveryCloudIpFinder [1]. Also, the ignite-extensions README says that each Ignite extension is published as a separate Maven artifact [2]. However, I cannot find org.apache.ignite:ignite-cloud-ext in Maven Central. At the same time, the old org.apache.ignite:ignite-cloud:2.13.0 artifact is still there and contains TcpDiscoveryCloudIpFinder [3]. Is this expected? Should users still use the old ignite-cloud:2.13.0, or should ignite-cloud-ext be published like the other cloud-related extensions? This came up because documentation snippets need a resolvable dependency for TcpDiscoveryCloudIpFinder. Thanks, Aleksandr [0] https://issues.apache.org/jira/browse/IGNITE-17137 [1] https://ignite.apache.org/docs/ignite2/latest/setup.html#enabling-modules [2] https://github.com/apache/ignite-extensions#apache-ignite-extensions-publication-and-versioning [3] https://central.sonatype.com/search?q=ignite-cloud
