javaplantuml/plantuml #898Not a task: already works

use --release flag of recent java versions

envgap__plantuml__plantuml-898

Original GitHub issue ↗Dated source checkout ↗Opened 2022-02-03

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 88947b9dc79283ec164e4cfa7d0f2a5c2c60df0f
Manifest: pom.xml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

plantuml/plantuml #898 · read the original issue

since java9 java supports a release flag for building to make sure the code is not using newer APIs. this is supported in maven and gradle:



* https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-release.html

* https://docs.gradle.org/current/userguide/building_java_projects.html



using this flag revealed two challenges:

- javac -target -source flags are not good enough guarantee compatiblity with old versions. use --release instead.

- plantuml uses java.time, introduced in java8. it was built always for java7 and the tools did not notice that installing and using real java7 gives compile and runtime errors.



would be cool if this does not happen any more in future.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]