You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(note that GHA Examples Dataflow v2 currently just setup a single Java version, which is not quite aligned with this pattern)
However, the test scope source of :example:java project is really a thin wrapper for the examples, which live in main scope. This actually means the pipeline is compiled with Java8, then run with Java11/17 runtime, which is not quite we want (GHA Dataflow v2 accidentally compile all sources with Java11/17 though)
We should clean up current setting to make the Example test to
all beam dependencies (e.g. Java core, runners) compile on Java 8 -- in alignment with released version
examples main and test src compile with given Java version
run test with given Java version
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
Abacn
changed the title
[Feature Request]: Support Compile Java Examples on Java 21
[Feature Request]: Compile Java Examples Main on Java 11/17/21 when run Java Example Tests
Oct 23, 2023
Abacn
changed the title
[Feature Request]: Compile Java Examples Main on Java 11/17/21 when run Java Example Tests
[Task]: Compile Java Examples Main on Java 11/17/21 when run Java Example Tests
Oct 23, 2023
What would you like to happen?
Currently we run Java Examples in different Java versions (11, 17), e.g.
In current tests (Jenkins, GHA Examples Dataflow v1), java home is always Java8, and it compile and run tests on Java 11/17, see
beam/.test-infra/jenkins/job_PostCommit_Java_Examples_Dataflow_V2_Java11.groovy
Line 48 in a94d29f
beam/.github/workflows/beam_PostCommit_Java_Examples_Dataflow_Java.yml
Lines 79 to 80 in a94d29f
(note that GHA Examples Dataflow v2 currently just setup a single Java version, which is not quite aligned with this pattern)
However, the test scope source of
:example:java
project is really a thin wrapper for the examples, which live in main scope. This actually means the pipeline is compiled with Java8, then run with Java11/17 runtime, which is not quite we want (GHA Dataflow v2 accidentally compile all sources with Java11/17 though)We should clean up current setting to make the Example test to
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: