+1
> On Dec 15, 2023, at 7:35 PM, Mick Semb Wever wrote:
>
>
>
>> I'd like to add Semver4j to the production dependencies. It is currently on
>> the test classpath. The library is pretty lightweight, licensed with MIT and
>> has no transitive dependencies.
>>
>> We need to represent the ker
I'd like to add Semver4j to the production dependencies. It is currently on
> the test classpath. The library is pretty lightweight, licensed with MIT
> and has no transitive dependencies.
>
> We need to represent the kernel version somehow in CASSANDRA-19196 and
> Semver4j looks as the right tool
+1
On Fri, Dec 15, 2023, at 1:29 PM, Derek Chen-Becker wrote:
> +1
>
> Semver4j seems reasonable to me. I looked through the code and it's
> relatively easy to understand. I'm not sure how easy it would be to replace
> CassandraVersion, but that's not an immediate concern I guess.
>
> Cheers,
+1
Semver4j seems reasonable to me. I looked through the code and it's
relatively easy to understand. I'm not sure how easy it would be to replace
CassandraVersion, but that's not an immediate concern I guess.
Cheers,
Derek
On Fri, Dec 15, 2023 at 2:56 AM Jacek Lewandowski <
lewandowski.ja...@g
Hi,
I'd like to add Semver4j to the production dependencies. It is currently on
the test classpath. The library is pretty lightweight, licensed with MIT
and has no transitive dependencies.
We need to represent the kernel version somehow in CASSANDRA-19196 and
Semver4j looks as the right tool for
