-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
Application update #5606
Comments
Clearly an interesting ticket |
Hello @DamnClin, |
@renanfranca : if you want help, it would be nice to review first the 1st PR. Could you, plz? |
Sorry I want to keep it :) (even if I don't know when I'll be able to work on it...) |
It's all right 😄 👍 |
Yes, I can 😃👍 |
We should provide an application update feature to ease migration / updates for existing applications.
I think a good way to tackle that is to have a
/update-modules
endpoint. This endpoint will basically apply the modules but it will remove some elements.The parts to remove from each module are to be defined in the final method of the
JHipsterModuleResource
builder, something like:.factories(dummy::buildModule, dummy::updateDelta)
(with the current.factory(...)
calling this new method with an empty delta).The
JHipsterModuleUpdateDelta
should allow definitions of differences between a "normal" apply and an update, the first 2 things I see are:pom.xml
orREADME.md
;With that, we'll then be able to make a new update screen. This screens starts by selecting an existing JHipster Lite project folder. Once done you have a list of applied modules that you can deselect if you want and a button to update the modules.
The text was updated successfully, but these errors were encountered: