Automatically restart wisdom:run when maven pom is modified #265

Closed
Riduidel opened this Issue Jul 9, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@Riduidel
Contributor

Riduidel commented Jul 9, 2014

To avoid the puzzling missing of routes of new assets, wisdom:run should restart when pom gets updated.

Mailing-list details :

Unfortunately so far every change to the pom requires a restart. This is
because it would actually require to relaunch Maven itself.

Adding a dependency is a bit tricky form the Maven point of you. It
needs to re-run the resolver and it may change the dependency graph
(because of transitive and conflicts). It’s not something we can easily
re-evaluate at runtime.

Ok, so simplest solution is to stop wisdom:run when pom is updated with
a nice message telling that it should be restarted ? Or, even better,
auto-restart wisdom:run with new pom (don't know how easy it is, as
command-line parameters should be re-applied) ?

Important points :

  • reuse command-line parameters (such as -Ddebug=5005)
  • Make sure debug sessions that are interrupted imply some kind of logging ("hey dude, i must restart, don't forget to reconnect your debugger !" - this is only an example message)

cescoffier added a commit that referenced this issue Jul 15, 2014

#265 - add the invoker dependency
Signed-off-by: Clement Escoffier <clement.escoffier@gmail.com>

@cescoffier cescoffier added the feature label Jul 25, 2014

@cescoffier cescoffier added this to the 0.6.2 milestone Jul 25, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment