One simple variant would be to use Maven with the Frontend Maven Plugin to install the JS dependecies and trigger the Angular CLI (ng build --prod) with it. With the Maven resources plugin it can than copy the folder with the compiled output into WEB-INF folder, and then you should basically be good to deploy. My setup at work is a bit more complex than that, as in I have a multi-module project, with seperate builds for backend, frontend, docker-image and several profiles. But the basic idea is still to have a one-step build with mvn clean install
Yes. Maven should be used if the company network allow. Maven is awesome for dependency management. But unfortunately, many company may block the internet or block some port or some other problems which make you cannot use Maven.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One simple variant would be to use Maven with the Frontend Maven Plugin to install the JS dependecies and trigger the Angular CLI (ng build --prod) with it. With the Maven resources plugin it can than copy the folder with the compiled output into WEB-INF folder, and then you should basically be good to deploy. My setup at work is a bit more complex than that, as in I have a multi-module project, with seperate builds for backend, frontend, docker-image and several profiles. But the basic idea is still to have a one-step build with
mvn clean installYes. Maven should be used if the company network allow. Maven is awesome for dependency management. But unfortunately, many company may block the internet or block some port or some other problems which make you cannot use Maven.