Mvn begone

[lordvlad]

will close #220

This PR aims to add alternatives to using mvn to create the final bundled theme jar.

mvn is an additional dependency, which needs to be installed, configured, has its own dependencies, and makes building in a CI (or even windows) more cumbersome than need be.

The keycloakify section in package.json has now an additional optional option called bundler, which accepts the values ['mvn', 'keycloakify', 'none']. If nothing is set, it will default to mvn. This option can also be overriden using the environment variable KEYCLOAKIFY_BUNDLER, accepting the same values of course.

• Choosing mvn (or defaulting) will result in an unchanged build
• Choosing none will not create a jar. The user will need to call maven or gradle or whatever themselves.
• Choosing keycloakify will use the new bundler code to create a jar file using nodejs libs only, no additional system libraries required.

In addition, this PR adds options to explicitely set artifactId using the keycloakify section in package.json, as well as options to override groupId and artifactId using the environment variables KEYCLOAKIFY_GROUP_ID and KEYCLOAKIFY_ARTIFACT_ID. The reasoning is, that companies often have naming conventions in place, which can now be upheld more easily.

Also added is an option to override the version from package.json using the environment variable KEYCLOAKIFY_VERSION. In our CI, for example, the version is determined from git tags and I don't want to patch package.json before running keycloakify.

[lordvlad]

In a follow-up PR, I intend to make build_keycloak directory configurable

[garronej]

Wow, nice 😻
I'm reviewing this this week end!

[garronej]

Hi @lordvlad,
Thank you very much for your work, it's realy great to drop the dependence to Maven and to have alle thoses new build options!

I documented everything: https://docs.keycloakify.dev/build-options#keycloakify.bundler

I made some little adjustmenet mostly related to type safery, you can check them out here: #240

The main thing I did is to set keycloakify to be the default bundler.
You did all this great work why not make it the default.

Again, many thanks,

Cheers

[garronej]

Re @lordvlad,
Unless it's my mistake again, I can't build with the new "bundler": "keycloakify" option.
When I set the option in the keycloakify-advanced-starter I get this runtime error:

I'm on Mac M1 v16.19.0. Update, same with v18.14.0

I've put back "mvn" as the default for now...

I do not exclude it being related to my changes. I'll have to investigate, in the meantime could you tell me if the latest release works for you on keycloakify-advanced-starter, thanks a lot.

[lordvlad]

I'll double check

[lordvlad]

follow-up in #241