Hi JB, In my opinion, it makes sense to include the eclipselink module by default, in all distributions. Without eclipselink, the distributables are pretty much useless for anything else than prototyping or evaluating.
By the way, for the admin tool, it really doesn't make any sense to ship it without eclipselink as it needs to connect to a persistent metastore. For the docker images, if all images have eclipselink included, I would suggest simply publishing: - For the Polaris server: one image named "apache/polaris" with two tags: "0.10.0-beta-incubating" and "latest" - For the admin tool: one image named "apache/polaris-admin-tool" with two tags: "0.10.0-beta-incubating" and "latest". If that can be of any help, the below command should do exactly that (you need to be logged into Docker): ./gradlew clean assemble \ -Dquarkus.container-image.tag=0.10.0-beta-incubating \ -Dquarkus.container-image.build=true \ -Dquarkus.container-image.push=true Thanks, Alex On Fri, Apr 18, 2025 at 8:12 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi folks > > As discussed yesterday during the community meeting, I propose we include > eclipselink module by default in Polaris server distribution and docker > image. > > I think it would help our users to easily start with Polaris. > I would like to include this for 0.10.0-beta-incubating release. > > Thoughts ? > > Regards > JB >
