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

When executing using a blueprint executable, we should not look for the blueprint locally. #24028

Closed
1 task
mshima opened this issue Oct 27, 2023 · 0 comments · Fixed by #24067
Closed
1 task

Comments

@mshima
Copy link
Member

mshima commented Oct 27, 2023

Overview of the issue

If we use a blueprint executable, the generators from the executable package should be used instead of using the locally installed.

Motivation for or Use Case

We should be consistent.

Reproduce the error
  • Install an older version locally
  • Install a new version globally
  • Run the global executable

The locally installed generators will be used.
If some generators are missing in any side like v7/v8, the can mix with each other.

Related issues
Suggest a Fix

Lookup for generators from the cli and don't override them with local.

JHipster Version(s)
JHipster configuration
Entity configuration(s) entityName.json files generated in the .jhipster directory
Browsers and Operating System
  • Checking this box is mandatory (this is just to show you read everything)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants