Custom page compile error

Q&A
1

I'm trying to update a custom page for the new BS version, but I have an issue during the compile with the plugin  gmaven-plugin

here the log fragment, 

 

[e[1;34mINFOe[m] e[1m--- e[0;32mgmaven-plugin:1.0:executee[m e[1m(default)e[m @ e[36mbonita-loge[0;1m ---e[m

[e[1;34mINFOe[m] e[1m------------------------------------------------------------------------e[m

[e[1;34mINFOe[m] e[1;31mBUILD FAILUREe[m

[e[1;34mINFOe[m] e[1m------------------------------------------------------------------------e[m

[e[1;34mINFOe[m] Total time: 18.112 s

[e[1;34mINFOe[m] Finished at: 2023-02-24T01:54:05-06:00

[e[1;34mINFOe[m] e[1m------------------------------------------------------------------------e[m

[e[1;31mERRORe[m] Failed to execute goal e[32morg.codehaus.groovy.maven:gmaven-plugin:1.0:executee[m e[1m(default)e[m on project e[36mbonita-loge[m: e[1;31mjava.lang.reflect.InaccessibleObjectException: Unable to make java.lang.String(char[],int,int,java.lang.Void) accessible: module java.base does not "opens java.lang" to unnamed module @20e9c165e[m -> e[1m[Help 1]e[m

[e[1;31mERRORe[m]

[e[1;31mERRORe[m] To see the full stack trace of the errors, re-run Maven with the e[1m-ee[m switch.

 

Can any one know how can i fix it?

 

2

Hi,

Check that your buildchain is using Java 11 and not Java 17 as it seems to be.

adding those properties in the project pom should do the trick:

11 11 ...

While it should work even using a Java 17 JDK, I recommend using a Java 11 JDK to avoid any bad surprises at runtime.

Also, check that you are using Groovy 3.0.x as a provided dependencies. You can inspire yourself from the generated pom when creating a rest api extension in groovy from a Studio or the maven archetype.

HTH
Romain