[
https://issues.apache.org/jira/browse/WICKET-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1250.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
first let me clarify that Start.java is meant to be used only during
development. That said - wicket can automatically reload markup and property
files - so there is no need to restart the server for those. Secondly, since it
is used for development it is most often launched with debug enabled - so JVM
wil use hotswap when .java files are modified and recompiled. This means that
there is no need to restart the app often. Most times you make a change,
refresh the page, and see the effect. Only when a change is made that the
hotswap cannot cope with a server restart is required.
It would be inefficient to restart the server any time any file is changed, so
i dont think this is a good idea...
> Automatically restart embedded Jetty on file change event
> ---------------------------------------------------------
>
> Key: WICKET-1250
> URL: https://issues.apache.org/jira/browse/WICKET-1250
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-quickstart
> Affects Versions: 1.3.0-rc2
> Environment: Any
> Reporter: Martin Grigorov
> Assignee: Igor Vaynberg
> Priority: Trivial
> Fix For: 1.3.1
>
> Attachments: WICKET-1250.patch
>
>
> For those of you who like the cool feature of maven-jetty-plugin to
> automatically restart the web application on change in the (main) sources I'm
> attaching a patch for wicket-quickstart archetype that brings this
> functionality in .../Start.java.
> Since it doesn't affect by any means the Wicket core functionalities it will
> be good to see this feature included in 1.3.0-final.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
