anton-vinogradov commented on code in PR #13266:
URL: https://github.com/apache/ignite/pull/13266#discussion_r3480713263
##########
docs/_docs/code-snippets/java/pom.xml:
##########
@@ -67,12 +68,48 @@
<artifactId>ignite-zookeeper</artifactId>
<version>${ignite.version}</version>
</dependency>
+ <dependency>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>ignite-aws-ext</artifactId>
+ <version>${ignite.extensions.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>ignite-azure-ext</artifactId>
+ <version>${ignite.extensions.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>${project.groupId}</groupId>
+ <!-- ignite-cloud-ext is not published to Maven Central, so use
the last released legacy artifact that still provides
TcpDiscoveryCloudIpFinder. -->
+ <artifactId>ignite-cloud</artifactId>
+ <version>2.13.0</version>
+ </dependency>
Review Comment:
Optional hardening — not blocking, the build is green as-is.
`ignite-cloud:2.13.0` also drags a transitive `ignite-core:2.13.0` (plus
jclouds 2.0.0 / guava 16.0.1) onto the gate classpath. Maven mediation already
prefers the direct 2.19 core, but for a *blocking* gate it's worth excluding it
explicitly so a second, 6-year-old core can never shadow 2.19:
```suggestion
<exclusions>
<!-- Keep only the current ignite-core on the snippets
classpath; this
legacy artifact otherwise also pulls in
ignite-core:2.13.0. -->
<exclusion>
<groupId>${project.groupId}</groupId>
<artifactId>ignite-core</artifactId>
</exclusion>
</exclusions>
</dependency>
```
--
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 comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
