Sorry for the late reply. Could you clarify why you think that? It is a bit hard to provide answers > to such feedback.
What I meant is that the PR [1] seems to provide a lot more than just Polaris related logic, which isn't a concern of the Polaris project. It's fine if it is trying to be a generic gradle plugin to allow start and end a server easily, but it could be somewhere else. Can we focus on the functionalities related to Polaris? For example, here are two options. Both seem to cover our requirements here, while Gretty is easier to use. Can we explore them? 1. ExecFork[2], which runs any Java / shell process in the background 2. Gretty[3], a Jetty / Tomcat dev-server with start/stop tasks [1]. https://github.com/apache/polaris-tools/pull/18 [2]. https://github.com/psxpaul/gradle-execfork-plugin [3]. https://github.com/gretty-gradle-plugin/gretty Yufei On Mon, Jun 2, 2025 at 12:44 AM Pierre Laporte <pie...@pingtimeout.fr> wrote: > On Thu, May 29, 2025 at 7:40 PM Yufei Gu <flyrain...@gmail.com> wrote: > > > I'm supportive if it adds value to both Polaris devs and users. > > > Ok thanks, I am glad we have agreement on the initiative, even if we still > have to discuss the implementation details. > > But, I don't think the Polaris project is in a position to provide a > > generic building infrastructure for integration tests. > > > > Could you clarify why you think that? It is a bit hard to provide answers > to such feedback. > > Can we list use cases the plugin tries to cover? I'd be happy to have a > > discussion session if needed. > > > > I believe I have listed the main high-level features in my first e-mail. > Are you referring to something else? > > Pierre >
