Application update

[DamnClin]

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:

• ignore a file to avoid reseting ex for pom.xml or README.md ;
• delete a file to handle moving files (like here Move authenticated user files #5605).

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.

[pascalgrimaud]

Clearly an interesting ticket

[pascalgrimaud]

@DamnClin : is it a duplicate of #2907 ?

[renanfranca]

Hello @DamnClin,
I am interested in working on that issue. Can I try to implement the WebServices part?

[pascalgrimaud]

@renanfranca : if you want help, it would be nice to review first the 1st PR. Could you, plz?

[DamnClin]

Sorry I want to keep it :) (even if I don't know when I'll be able to work on it...)

[renanfranca]

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 😄 👍

[renanfranca]

@renanfranca : if you want help, it would be nice to review first the 1st PR. Could you, plz?

Yes, I can 😃👍