Dany, possibly you can try to shade [1] h2, i.e. rebuild ignite project from
scratch with a bit of modifications?
[1] https://maven.apache.org/plugins/maven-shade-plugin/
>Hi,
>
>Regarding the H2 deadlock, do you have an expected ETA for post-release 2.13?
>All our projects are currently block because H2 is such problematic we cannot
>build project using it.
>
>Thank you
>
>>On Feb 7, 2022, at 1:08 AM, Alex Plehanov < [email protected] > wrote:
>>Hello,
>>
>>Unfortunately, update to the newest H2 version is not possible, since H2
>>removed the Ignite support [1].
>>Currently, the new SQL engine for Ignite is under development. The first beta
>>release of this engine is planned to Apache Ignite 2.13 version [2]. But it
>>still requires the ignite-indexing module, which requires H2. This problem
>>will be settled in one of the next versions after 2.13.
>>
>>[1]: https://github.com/h2database/h2database/pull/2227
>>[2]: https://lists.apache.org/thread/yck17qhcgg2qmzp374q69xvlhb9ocwhh
>>
>>ср, 2 февр. 2022 г. в 19:13, tore yang < [email protected] >:
>>>Hi,
>>>
>>>Today the library h2 1.4.197 was banned by my firm for security issue, as a
>>>result my i gnite applications (running on version 2.12.0) can not be
>>>released, When I upgrade to version like 2.1.210, the clients failed to
>>>connect to the cluster, complaining no class definition for
>>>org.h2.index.BaseIndex.
>>>I guess Apache Ignite doesn't support h2 2.1.210 as of now? if so when it's
>>>going to support?
>>>
>>>
>>>Regards,
>>>
>>>Tao
>>>
>>>
