This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push: new c0377dc Update Readme.md c0377dc is described below commit c0377dcf2264ec72cf70d3fe92ffbddfddec590a Author: Claus Ibsen <claus.ib...@gmail.com> AuthorDate: Thu Aug 23 14:07:45 2018 +0200 Update Readme.md --- examples/camel-example-reload/Readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/camel-example-reload/Readme.md b/examples/camel-example-reload/Readme.md index 48142c8..ea121f1 100644 --- a/examples/camel-example-reload/Readme.md +++ b/examples/camel-example-reload/Readme.md @@ -9,7 +9,7 @@ the route on-the-fly. The reload only applies to Camel routes, eg the `<route>` elements inside `<camelContext>`. For changes to Spring or OSGi Blueprint `<bean>`s or Java code, then alternative reload strategies -can be used. For example Spring Boot has a live reload tool, which you can try with the `camel-example-spring-boot-live-reload` example. OSGi Blueprint can be reloaded using Karaf container where you can run the `dev:watch *` command and +can be used. OSGi Blueprint can be reloaded using Karaf container where you can run the `dev:watch *` command and then rebuild your code with `mvn install` which triggers Karaf to redeploy the bundle when the SNAPSHOT jar is updated in the local Maven repository. ### How to try