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.

Sign up for GitHub

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

Jump to bottom

Orchestrate in the pom.xml client and server part without spring-boot #14

Closed
ghost opened this issue Jul 7, 2019 · 2 comments
Closed

Orchestrate in the pom.xml client and server part without spring-boot #14

ghost opened this issue Jul 7, 2019 · 2 comments
Labels
Feature New feature
Projects
nodejs blueprint
Milestone
1.0.0-alpha.2

Comments

@ghost
Copy link

ghost commented Jul 7, 2019 •
edited by ghost
Loading

@hadirsa, I can't assign you this issue because you aren't in the jhipster group.
Don't worry, you will be soon :) . So I have moved the activity discussed in gitter from the kanban board and tag you.
For every question feel free to ask me. Thank you very much for your contribution!
@ghost ghost created this issue from a note in nodejs blueprint (To do) Jul 7, 2019
@ghost ghost moved this from To do to In progress in nodejs blueprint Jul 7, 2019
@ghost ghost added the Feature New feature label Jul 7, 2019
@ghost ghost moved this from In progress to To do in nodejs blueprint Aug 13, 2019
@ghost ghost moved this from To do to In progress in nodejs blueprint Aug 19, 2019
@ghost
Copy link
Author

ghost commented Aug 19, 2019 •
edited by ghost
Loading

@hadirsa , thanks @ivangsa for the #21, you can decided a way to orchestrate in monolithic app client and server generation. Feel free to decide a server folder and how to connect client build with server. So start with this issue. Thanks

@ghost
Copy link
Author

ghost commented Aug 20, 2019 •
edited by ghost
Loading

I have risolved the issue with the last commit.

To run all the generated type app, now we run mvnw package with -Pdev or -Pprod profile in root folder

@ghost ghost closed this as completed Aug 20, 2019
nodejs blueprint automation moved this from In progress to Done Aug 20, 2019
@ghost ghost added this to the 1.0.0-alpha.1 milestone Sep 19, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature New feature
Projects
nodejs blueprint
  
Done
Milestone
1.0.0-alpha.2
Development

No branches or pull requests
0 participants