Stefano Cordio

According to https://github.com/spockframework/spock/issues/1897#issuecomment-1971450856, this isn't something to be solved in AssertJ, so I'm closing the issue but happy to reconsider in case of new arguments.

> AssertJ does not play well here with the Groovy semantic @AndreasTu is the Groovy semantic and the `asBoolean` as a reserved name documented somewhere? The [power assertions](https://groovy-lang.org/testing.html#_power_assertions) section doesn't...

@AndreasTu looking at the plain Groovy example, what is the purpose of prefixing the `assertThat` call with `assert`? We have [some basic Groovy integration tests](https://github.com/assertj/assertj/tree/main/assertj-tests/assertj-integration-tests/assertj-core-groovy/src/test/groovy/org/assertj/core/tests/groovy) and none of them uses...

> The only additional thing I could see, is to open a ticket at Groovy and ask them I was halfway through it when I realized that it's the usage...

I'm reconsidering my previous suggestion to add a new `ScrollingRepositoryItemReader`. Maybe there is a way to generalize `RepositoryItemReader` and make it work with the new scrolling patterns, without breaking existing...

A working example: ascopes/java-compiler-testing#806

To give more freedom to external modules like in https://github.com/assertj/assertj-vavr/issues/232#issuecomment-3067007850, we will target 3.27.4 to address this and forward-port the corresponding changes to 4.0.0.

As discussed internally, we'll use the opportunity to enable snapshot publishing.

Done in #3881.

Hi @alihmzyv, sorry for the late answer and thanks for offering to help! The issue is quite undefined at the moment... we'd need to investigate how to define such CI...