Okta Spring Boot Starter VS frontend-maven-plugin

Okta also now has an Okta Spring Boot starter. I didn't use it in my first experiment, but I'm a big fan of it after the last few years! It dramatically simplifies configuration and makes securing your apps with OAuth 2.0 and OIDC easy. It's a thin wrapper around Spring Security's resource server, OAuth client, and OIDC features. Not only that, but it works with Okta Workforce Identity, Okta Customer Identity (aka Auth0), and even Keycloak.

looks like these, the api, sdk, and the httpclient are basically what the okta saml spring boot starter are wrapping (https://github.com/okta/okta-spring-boot/blob/master/okta-spring-boot-starter/pom.xml). so you should be able to call those directly.

okta: Okta Spring Boot Starter that helps OAuth 2.0 and OIDC configuration

If you'd rather use Auth0, that's possible too! First, you'll need to use the Spring Security dependencies as mentioned above. The Okta Spring Boot starter currently doesn't work with Auth0.

Install Node.js Frontend Maven Plugin Gradle Plugin for Node

To build and package your React app with Maven, you can use the frontend-maven-plugin and Maven's profiles to activate it. Add properties for versions and a section to your pom.xml.

In JavaScript land this stuff is done via npm instead. There is a tool for bridging Maven and NPM land stuff https://github.com/eirslett/frontend-maven-plugin but then you are really talking about maintaining two complete stacks. At some point then you might as well just check out something like SvelteKit and Prisma.

Ever considered using eirslett/frontend-maven-plugin? It kind of takes care of a lot of heavy loading, such as setting the environment in order for your project to be built correctly.

You should be able to get away with maven frontend plugin. It will run scripts in your package.json. from there make sure your build output goes in the right place, probably resources/META-INF or something like that.

Sass is an interesting language for generating CSS files that I'm currently trying to play around with. Unfortunately, the existing sass-maven-plugin are based on obsolete implementations, and adding a dependency on npm seems really cumbersome.

3) Bunding into a .jar file : packaging the frontend with the backend into a single JAR file was very confusing. I found the solution using two maven plugins. The first plugin was frontend-maven-plugin which down loads everything that our frontend needs and runs the build command. The second plugin was the Apache Maven Resources Plugin which handles the copying of project resources to the output directory. The combination of these two plugins will give us the ability to run the command of mvnw clean package and have an executable JAR file in the output directory, which we can then execute.

The frontend-maven-plugin is useful to install NodeJS and NPM on the phase of Maven project build. First you add it to POM.xml file:

This is my first time posting here. I have a project that requires me to use Maven (pom.xml) for the build process. I have been using https://github.com/eirslett/frontend-maven-plugin for quite a while and really like it. The frontend-maven-plugin is really neat because it downloads node/npm and saves is in a temporary location within the repo and those local node/npm executables are then used to run certain commands. That way, you can guarantee that the environment running the build has the necessary (pinned to a version) dependencies.