Get GHA working on master

[jvanzyl]

I tried this for the first time, and it appears that the scala module is having issues.

@mosabua is the scala module been having issues lately?

My suggestion would be to put each of the modules that are not working on their own branch, and if anyone wants to tackle fixing them up they can.

[laeubi]

Maybe instead of an own branch simply deactivate the module in maven (for now)?

[jvanzyl]

Sure, I can do that.

[jvanzyl]

Ok, the GHA CI is working now. Right now it's using Java11 to build, is this an issue for anyone? I'll wait until the morning to cut a release to see if anyone wants me to set this to Java8 for any reason.

@headius is Java11 an issue for JRuby?

[mosabua]

I think Java 11 is ok for JRuby .. but not sure if everything will build on the jruby module ..

Scala has been fine

[jvanzyl]

I'll let @headius comment on JRuby, and @lefou can take what time he needs if he can get the scala module working.

[lefou]

Scala Dialect is ready, see #234

[headius]

JRuby still supports Java 8 for at least the next major version, so whatever happens we'd like to see the polyglot plugins support Java 8 a bit longer. Building with 11 would be fine if the artifacts produced are effectively -release 8.

[jvanzyl]

@lefou Can the Scala module build with Java8? If there are no Java11 specific features needed I'll just build with Java8 for this release. After this release we can coordinate a release where we build with Java11.

[lefou]

@jvanzyl Of course, it can. CI is already building with Java 8 and Java 11.

Do you plan to automate the release via GHA, too?

[jvanzyl]

Ok, I'll do the release using Java8. I'll add some release actions for the next release. I have code now to do all the PGP signing actions in Java, but I need want to generate a sub-key, store that key as a PEM resource in GitHub secrets and then use that for the signing.

[jvanzyl]

Build is working, 0.4.7 release made.