Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0054487 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
feature request | [Openbravo ERP] A. Platform | minor | have not tried | 2024-01-29 11:54 | 2024-02-22 14:50 | |||
Reporter | shuehner | View Status | public | |||||
Assigned To | Triage Platform Base | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Review Assigned To | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0054487: Avoid compiler warning about implicit annotation processing by disabling it using -proc:none (selenium code) | |||||||
Description | Until Java<21 the java compiler implicitely looked for and ran any annotation processor found on the classpath. Since Java21 the following warning is shown to inform users about upcoming change. [javac] Note: Annotation processing is enabled because one or more processors were found [javac] on the class path. A future release of javac may disable annotation processing [javac] unless at least one processor is specified by name (-processor), or a search [javac] path is specified (--processor-path, --processor-module-path), or annotation [javac] processing is enabled explicitly (-proc:only, -proc:full). [javac] Use -Xlint:-options to suppress this message. [javac] Use -proc:none to disable annotation processing. This is companion issue to 54452 (which is for backoffice) and is about: - backoffice-test - mobile-test repositories. | |||||||
Steps To Reproduce | Running compile with jdk-21 | |||||||
Proposed Solution | Not knowingly needing any annotation processing idea is to explicitely disable it using -proc:none If usage should show up later it is better to explicitely notice this (i.e. in CI) and then work on properly supporting that. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |||||||||||||||
|
Notes | |
(0159857) hgbot (developer) 2024-01-29 12:22 |
Merge Request created: https://gitlab.com/openbravo/ci/mobile-test/-/merge_requests/359 [^] |
(0159870) hgbot (developer) 2024-01-29 12:50 |
Merge Request created: https://gitlab.com/openbravo/ci/backoffice-test/-/merge_requests/36 [^] |
(0160585) hgbot (developer) 2024-02-09 19:56 |
Repository: https://gitlab.com/openbravo/ci/mobile-test [^] Changeset: 87245514dbb6879e6f6f3194a16f0ba41e59f3e4 Author: adrian.blasco <adrian.blasco@openbravo.com> Date: 09-02-2024 10:59:42 URL: https://gitlab.com/openbravo/ci/mobile-test/-/commit/87245514dbb6879e6f6f3194a16f0ba41e59f3e4 [^] ISSUE-54487: Disable annotation processing with -proc:none to avoid warnings Until Java<21 the java compiler implicitely looked for and ran any annotation processor found on the classpath. Since Java21 the following warning is shown to inform users about upcoming change of default for this policy. [javac] Note: Annotation processing is enabled because one or more processors were found [javac] on the class path. A future release of javac may disable annotation processing [javac] unless at least one processor is specified by name (-processor), or a search [javac] path is specified (--processor-path, --processor-module-path), or annotation [javac] processing is enabled explicitly (-proc:only, -proc:full). [javac] Use -Xlint:-options to suppress this message. [javac] Use -proc:none to disable annotation processing. - Add a new ant property javac.proc to specify value to be used via <compilerarg line> for all our various javac invocations - For the value use -proc:none to explicitely disable annotation processing during compilation <compilearg line> was chosen as with <compiler arg> value run into some cornercase issues in case value was empty. This is companion change for 54452 (in backoffice repo) --- M build.xml --- |
(0160586) hgbot (developer) 2024-02-09 19:56 |
Merge request merged: https://gitlab.com/openbravo/ci/mobile-test/-/merge_requests/359 [^] |
(0160587) hgbot (developer) 2024-02-09 19:57 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/ci/backoffice-test [^] Changeset: 333e1db3a12e663e523a94f327f602d1c214a811 Author: Stefan Huehner <stefan.huehner@openbravo.com> Date: 09-02-2024 19:54:24 URL: https://gitlab.com/openbravo/ci/backoffice-test/-/commit/333e1db3a12e663e523a94f327f602d1c214a811 [^] Fixed ISSUE-54487: Disable annotation processing with -proc:none to avoid warnings Until Java<21 the java compiler implicitely looked for and ran any annotation processor found on the classpath. Since Java21 the following warning is shown to inform users about upcoming change of default for this policy. [javac] Note: Annotation processing is enabled because one or more processors were found [javac] on the class path. A future release of javac may disable annotation processing [javac] unless at least one processor is specified by name (-processor), or a search [javac] path is specified (--processor-path, --processor-module-path), or annotation [javac] processing is enabled explicitly (-proc:only, -proc:full). [javac] Use -Xlint:-options to suppress this message. [javac] Use -proc:none to disable annotation processing. - Add a new ant property javac.proc to specify value to be used via <compilerarg line> for all our various javac invocations - For the value use -proc:none to explicitely disable annotation processing during compilation <compilearg line> was chosen as with <compiler arg> value run into some cornercase issues in case value was empty. This is companion change for 54452 (in backoffice repo) --- M build.xml --- |
(0160588) hgbot (developer) 2024-02-09 19:57 |
Merge request merged: https://gitlab.com/openbravo/ci/backoffice-test/-/merge_requests/36 [^] |
(0161138) hgbot (developer) 2024-02-22 14:50 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/ci/backoffice-test [^] Changeset: 333e1db3a12e663e523a94f327f602d1c214a811 Author: Stefan Huehner <stefan.huehner@openbravo.com> Date: 09-02-2024 19:54:24 URL: https://gitlab.com/openbravo/ci/backoffice-test/-/commit/333e1db3a12e663e523a94f327f602d1c214a811 [^] Fixed ISSUE-54487: Disable annotation processing with -proc:none to avoid warnings Until Java<21 the java compiler implicitely looked for and ran any annotation processor found on the classpath. Since Java21 the following warning is shown to inform users about upcoming change of default for this policy. [javac] Note: Annotation processing is enabled because one or more processors were found [javac] on the class path. A future release of javac may disable annotation processing [javac] unless at least one processor is specified by name (-processor), or a search [javac] path is specified (--processor-path, --processor-module-path), or annotation [javac] processing is enabled explicitly (-proc:only, -proc:full). [javac] Use -Xlint:-options to suppress this message. [javac] Use -proc:none to disable annotation processing. - Add a new ant property javac.proc to specify value to be used via <compilerarg line> for all our various javac invocations - For the value use -proc:none to explicitely disable annotation processing during compilation <compilearg line> was chosen as with <compiler arg> value run into some cornercase issues in case value was empty. This is companion change for 54452 (in backoffice repo) --- M build.xml --- |
Issue History | |||
Date Modified | Username | Field | Change |
2024-01-29 11:54 | shuehner | New Issue | |
2024-01-29 11:54 | shuehner | Assigned To | => Triage Platform Base |
2024-01-29 11:54 | shuehner | Modules | => Core |
2024-01-29 11:54 | shuehner | Triggers an Emergency Pack | => No |
2024-01-29 11:54 | shuehner | Issue generated from | 0054452 |
2024-01-29 11:54 | shuehner | Relationship added | related to 0054452 |
2024-01-29 12:22 | hgbot | Note Added: 0159857 | |
2024-01-29 12:50 | hgbot | Note Added: 0159870 | |
2024-01-29 17:58 | shuehner | Relationship added | blocks 0054449 |
2024-02-09 19:56 | hgbot | Note Added: 0160585 | |
2024-02-09 19:56 | hgbot | Note Added: 0160586 | |
2024-02-09 19:57 | hgbot | Resolution | open => fixed |
2024-02-09 19:57 | hgbot | Status | new => closed |
2024-02-09 19:57 | hgbot | Note Added: 0160587 | |
2024-02-09 19:57 | hgbot | Note Added: 0160588 | |
2024-02-22 14:50 | hgbot | Note Added: 0161138 |
Copyright © 2000 - 2009 MantisBT Group |