Project:
| View Revisions: Issue #54588 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0054588: Update ecj compile jar in eclipse-warnings to be able to check up to jdk21, keep older ecj for use with 11 | ||
| Revision | 2024-02-06 15:17 by shuehner | ||
| Description | Currently the eclipse-warnings repo https://gitlab.com/openbravo/tools/ci/eclipse-warnings [^] Is restricting the 'compliance' to java version parameter to a max 13 (so checking against jdk13). We should update the ecj compiler in there to be able to check up to the latest jdk 21 (LTS) Updating to ecj>4.27 requires to run the tool with java17 itself. Always using ecj-4.30.jar (running with java17) causes warnings/errors when being used for old backoffice versions which do not support 17 cleanly or at all (i.e. jdk15 nashorn removal). |
||
| Revision | 2024-02-06 15:16 by shuehner | ||
| Description | Currently the eclipse-warnings repo https://gitlab.com/openbravo/tools/ci/eclipse-warnings [^] Is restricting the 'compliance' to java version parameter to a max 13 (so checking against jdk13). We should update the ecj compiler in there to be able to check up to the latest jdk 21 (LTS) Updating to ecj>4.27 requires to run the tool with java17 itself. But just using ecj-4.30.jar running with java17 always causes warnings/errors when being used for old backoffice version which do not support 17 (i.e. jdk15 nashorn removal). |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |