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
Hi all,
as @gmarziou and @mraible have indicated, we can replace the maven tool with a simple node script to manage running and building profiles (dev or prod), and in future other profiles (as example CI/CD and so on). In a standard jhipster app, only for a monolithic app with the client there is the maven frontend plugin to install and manage node/npm version, but in this blueprint, that is mandatory to have nodejs also for backend, we can avoid to use it, and add only a constraint of a nodejs minimum version, according the client and server requirement. This mean reason is explainable, as said @mraiblehere, the target is a common nodejs developer. Do you agree? thanks for the attention.
The text was updated successfully, but these errors were encountered:
Hi all,
as @gmarziou and @mraible have indicated, we can replace the maven tool with a simple node script to manage running and building profiles (dev or prod), and in future other profiles (as example CI/CD and so on). In a standard jhipster app, only for a monolithic app with the client there is the maven frontend plugin to install and manage node/npm version, but in this blueprint, that is mandatory to have nodejs also for backend, we can avoid to use it, and add only a constraint of a nodejs minimum version, according the client and server requirement. This mean reason is explainable, as said @mraible here, the target is a common nodejs developer. Do you agree? thanks for the attention.
The text was updated successfully, but these errors were encountered: