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

Remove CLI and use jhipster CLI #2

Closed
deepu105 opened this issue Jun 14, 2019 · 2 comments
Closed

Remove CLI and use jhipster CLI #2

deepu105 opened this issue Jun 14, 2019 · 2 comments
Labels
question Further information is requested
Milestone

Comments

@deepu105
Copy link
Member

Lets not use a separate CLI here. Blueprints should use jhipster cli and specify the blueprint name so that when we get multiple blueprint working we can interop without issues. Also it avoids fragmentation

@ghost
Copy link

ghost commented Jun 15, 2019

Hi @deepu105, I have added a cli script as kotlin blueprint.
it is not tested yet, and in my opinion is not a problem to provide another type of installation, also because it's the same jhipster running way (change only the installation and the execution command)

@ghost ghost added the question Further information is requested label Aug 13, 2019
@ghost
Copy link

ghost commented Aug 20, 2019

cli removed in #21. Thanks

@ghost ghost closed this as completed Aug 20, 2019
@ghost ghost added this to the 1.0.0-alpha.1 milestone Sep 19, 2019
ghost pushed a commit that referenced this issue Jun 10, 2021
Automatically set createdBy, createdDate, lastModifiedBy and lastModi…
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant