prototype7421-gif opened a new issue, #1718:
URL: https://github.com/apache/wicket/issues/1718
### Description
When building the Wicket `master` branch (11.0.0-SNAPSHOT) using a
modern/early-access JDK (JDK 27), the build consistently fails at the
`wicket-extensions` module.
The `resources-optimizer-maven-plugin` attempts to compress
`wicket-veil.min.js`, which is already minified. The underlying Google Closure
Compiler throws multiple `JSC_NON_CONST_DEFINE` errors. This behavior is likely
triggered by stricter memory/parsing behaviors in modern Java runtimes clashing
with the older Closure Compiler version embedded in the plugin (v2.7.9).
### Error Log Snippet
```text
[ERROR] JSC_NON_CONST_DEFINE. @define $jscomp.ASSUME_ES2020 has already been
set at src/com/google/javascript/jscomp/js/util/defines.js:39:8. at
C:/.../wicket-extensions/target/classes/org/apache/wicket/extensions/ajax/veil/wicket-veil.min.js
line 1 : 287
...
[ERROR] Failed to execute goal
org.primefaces.extensions:resources-optimizer-maven-plugin:2.7.9:optimize
(default) on project wicket-extensions: Resources optimization failure.
### Environment
Wicket Version: 11.0.0-SNAPSHOT (master branch)
Java Version: JDK 27
OS: Windows
### Proposed Solution
Merge the multi-line {@link} tags in package.html into a single continuous
line.
For example, changing:
HTML
{@link
org.apache.wicket.util.diff.Diff}
to:
HTML
{@link org.apache.wicket.util.diff.Diff}
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
