You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In other geOrchestra webapps, where a build step which makes use of nodejs is involved, we do use the frontend-maven-plugin instead of having a seperate build phase outside of maven:
The main advantage it could bring to the current situation is to have a simplified build, as the maven command could also take care of generating JS / static resources, simplifying e.g. CICD processes as well. From my PoV, it would have avoided having a webapp generated without the frontend resources (see my previous issue).
What is your opinion on it, do you think it could be a good addition to the project ?
The text was updated successfully, but these errors were encountered:
In other geOrchestra webapps, where a build step which makes use of nodejs is involved, we do use the
frontend-maven-plugin
instead of having a seperate build phase outside of maven:https://github.com/georchestra/georchestra/blob/19.04/console/pom.xml#L505-L535
The main advantage it could bring to the current situation is to have a simplified build, as the maven command could also take care of generating JS / static resources, simplifying e.g. CICD processes as well. From my PoV, it would have avoided having a webapp generated without the frontend resources (see my previous issue).
What is your opinion on it, do you think it could be a good addition to the project ?
The text was updated successfully, but these errors were encountered: