Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve module auto detection #8698

Open
gzsombor opened this issue Jan 21, 2024 · 0 comments
Open

Improve module auto detection #8698

gzsombor opened this issue Jan 21, 2024 · 0 comments

Comments

@gzsombor
Copy link
Member

gzsombor commented Jan 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@gzsombor @pascalgrimaud and others