rahulshishodia commented on issue #15042:
URL: https://github.com/apache/grails-core/issues/15042#issuecomment-3791009157
Hi @jamesfredley,
The Grails 7 migration is complete for this plugin in my dev branch.
However, some backing dependencies are deprecated (for example, Pegdown), and
it’s not possible to make the plugin fully Java 17 compatible without moving to
an alternative framework such as Flexmark.
So we have two possible migration paths. Please let me know which approach
you’d prefer:
a) Keep Pegdown and migrate to Grails 7
In this case, client applications will need Java 17 compatibility
workarounds by adding JVM `--add-opens` flags in their bootRun configuration
(and also in production). Example:
```groovy
bootRun {
jvmArgs = [
"--add-opens=java.base/java.lang=ALL-UNNAMED"
]
}
```
This keeps Pegdown working on Java 17 but is a workaround.
b) Migrate to Flexmark along with Grails 7
This removes the need for JVM workarounds and provides clean Java 17
compatibility. But has breaking changes in plugin api, for example
`customizeFlexmark` in config params instead of `customizePegdown` and other
minor changes due to how Flexmark interprets and convert to and from markdown.
Please let me know how this should be done.
--
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]
