Thanks for sharing it here. If all we need is to start a Polaris instance, run the tests, and shut it down, a 7 k-line Apprunner plugin feels like using a sledgehammer on a thumbtack. Would a lightweight Testcontainers wrapper, or even a simple Gradle exec hook would cover the use cases?
Yufei On Tue, May 27, 2025 at 11:17 AM Pierre Laporte <pie...@pingtimeout.fr> wrote: > Hi all > > The PR polaris-tools#18 (https://github.com/apache/polaris-tools/pull/18/) > aims at adding the ability to run temporary Polaris servers using Maven and > Gradle. It is a successor to https://github.com/apache/polaris/pull/785 > that was initially proposed for the apache/polaris repository. > > The goal is to make it easy for users to develop integration tests for > their applications, without relying on a central Polaris server. > > As Yufei asked some questions in the PR comments, let me repeat the answers > here so that everybody has the same context. > > The PR contains code to support a Groovy DSL in Gradle. This is because, > even if Polaris uses Kotlin for all Gradle build files, some users may be > using Groovy. So in order to make it possible for them to leverage the > Apprunner, a Groovy DSL is supported. > > Similarly, the PR contains code for Maven MOJOs to start and stop Polaris > servers. Those are intended to be used in Java project that use Maven as > their build tools. That way, the Apprunner supports the two mainstream > Java build systems. > > This thread is created to continue discussing the Apprunner integration in > the polaris-tools repository and answer any remaining question. > > WDYT? > > -- > > Pierre >
