[
https://issues.apache.org/jira/browse/IGNITE-14845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476050#comment-17476050
]
Nicolas Garcin commented on IGNITE-14845:
-----------------------------------------
I think it would be wiser to upgrade to 2.0.206 as previous versions have a
very high vulnerability, see
https://mvnrepository.com/artifact/com.h2database/h2.
> Upgrade H2 or enclose in Ignite classpath
> -----------------------------------------
>
> Key: IGNITE-14845
> URL: https://issues.apache.org/jira/browse/IGNITE-14845
> Project: Ignite
> Issue Type: Improvement
> Components: h2-limitation
> Affects Versions: 2.10
> Reporter: Elias Balasis
> Priority: Major
>
> When using Apache Ignite with SpringBoot or other dependency chains we are
> forced to downgrade H2 to 4.1.197 which breaks other relationships besides
> making the classpath fragile and less maintainable besides causing runtime
> conflicts.
> It would be very welcome if H2 could be upgraded to 4.1.200
> Ideally, H2 should be enclosed in Apache Ignite classpath which is the way
> GridGain Ignite handles this problem, without a direct dependency on H2
> itself but enclosing H2 instead in internal packages.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
