Add optional eclipselink dependency to build and include as build arg in Dockerfile

[collado-mike]

Description

#53 removed the eclipselink subproject as a dependency of the polaris-service build. As an optional dependency, it makes sense to not include it automatically. However, users will need a way to include the subproject in the service jar and in the output Dockerfile.

This updates the gradle build to accept an optional eclipseLink property that includes the subproject in the shadow jar. Additionally, there's a corresponding ECLIPSELINK arg in the docker build.

While testing this, I also updated the Dockerfile to specify an ENTRYPOINT and a CMD so that it's easy to point to a different polaris-server.yml file and/or execute a different command (such as the bootstrap or upcoming purge command) from the same docker image.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Ran

docker build . --build-arg ECLIPSELINK=true -t polaris:latest

then I updated my local polaris-server.yml file to specify eclipse-link as the metaStoreManager and ran with

docker run -p 8181:8181 -v ${PWD}:/conf polaris:latest server /conf/polaris-server.yml

Confirmed the following was in the server output at startup:

INFO  [2024-08-07 22:45:32,934 - 640   ] [main] [] i.p.service.PolarisApplication: Initializing PolarisCallContextCatalogFactory for baseCatalogType polaris, metaStoreManagerType io.polaris.extension.persistence.impl.eclipselink.EclipseLinkPolarisMetaStoreManagerFactory@22590e3e

• Test A
• Test B

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

Please delete options that are not relevant.

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue
• I have signed and submitted the ICLA and if needed, the CCLA. See Contributing for details.

[snazy]

Would it harm to unconditionally include it as a runtimeOnly dependency?

For integration-testing, we could also add a separate test-suite to :polaris-service that has :polaris-eclipselink as well.

[snazy]

It's relatively easy to add such a test-suite:

testing {
  suites {
    register("intTestEclipselink", JvmTestSuite::class.java) {
      useJUnitJupiter()

      dependencies {
        implementation(project())
        implementation(project(":polaris-eclipselink") // this would be an implementation-dependency for the suite
      }

      targets {
        all {
          tasks.named("check").configure { dependsOn(testTask) }
        }
      }
    }
}

[collado-mike]

I opened #125 to discuss whether we should include the dependency by default

[MonkeyCanCode]

Raised similar PR for this: #118

I think we still needed to add h2 lib for default persistent backend for extension/persistence/eclipselink/build.gradle.kts.

[sfc-gh-aixu]

LGTM.

[collado-mike]

Merging this after discussion in #125

[aihuaxu]

LGTM.