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
Currently, if a project is not generated with JHipster-Lite - maybe, because it was generated with Classic JHipster - the tool could not detect, that certain behaviours are already there, so re-running is not needed.
Like, if there is already a pom.xml, the maven initialization is not strictly needed.
It would be nice, if every module could provide an auto-detection feature, which could be called by JHLite, whenever
a project is opened
all of the module's dependency are satisfied
to check, if that module should also be considered as executed.
So for example, the MAVEN_JAVA module could check for pom.xml, the MAVEN_WRAPPER could check if mvnw script is there, etc.
The text was updated successfully, but these errors were encountered:
Currently, if a project is not generated with JHipster-Lite - maybe, because it was generated with Classic JHipster - the tool could not detect, that certain behaviours are already there, so re-running is not needed.
Like, if there is already a pom.xml, the maven initialization is not strictly needed.
It would be nice, if every module could provide an auto-detection feature, which could be called by JHLite, whenever
to check, if that module should also be considered as executed.
So for example, the MAVEN_JAVA module could check for pom.xml, the MAVEN_WRAPPER could check if mvnw script is there, etc.
The text was updated successfully, but these errors were encountered: