-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: build and run from Docker Support #5
Conversation
Fix gradle
d9a3197
to
ee5db7b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get the use case for this.
I started using docker recently but if you want to test the blueprint against different version of generator-jhipster, probably is better to use generator-jhipster docker with custom command and rely on generator-jhipster blueprint auto install.
Build and run the generator from docker image support added. The main aim and motivation behind doing this is, because of a no. of different jhipster blueprints are there, which are compatible and works with the different version of jhipster and also might be incompatible with other blueprints or versions of jhipster. Signed-off-by: Pratik Raj <[email protected]>
ee5db7b
to
1636b27
Compare
This PR was closed due to a force-push on main branch.
|
Build and run the generator from docker image support added.
The main aim and motivation behind doing this is, because
of a no. of different jhipster blueprints are there,
which are compatible and works with the different version of jhipster
and also might be incompatible with other blueprints or versions of jhipster.
Signed-off-by: Pratik Raj [email protected]