Hi Cedric,
As a first step I think it will be good if the user application has control
whether to re-init the app or not.
As we talked in IRC it would be good if the broadcasted event brings info
what has changed. This way the user code can decide whether there is a need
to restart the app.
By
Am 01.08.13 09:55, schrieb Martin Grigorov:
Michael,
On Thu, Aug 1, 2013 at 9:48 AM, Michael Mosmann mich...@mosmann.de wrote:
Only to be sure.. You know the run-jetty-run eclipse plugin?
All I know about this project is that Eelco started it.
I think this project is very usefull. But
Hi Martin,
I will collect what has changed and log it out. I can add a property to
auto restart the application as well. The current status of this POC is
unbounded, I only tested it with small apps and I don't know if it will
properly reload page classes for example if we don't reinit the
You should commit with some delay between master and wicket-6.x because
otherwise wicket-examples' test fail to use the same http port...
On Fri, Aug 2, 2013 at 1:55 PM, build...@apache.org wrote:
The Buildbot has detected a new failure on builder wicket-branch-6.x while
building wicket.
Should we do something to avoid that? Could the different branches use
different ports? Or some buildbot-config?
On Fri, Aug 2, 2013 at 7:58 AM, Martin Grigorov mgrigo...@apache.orgwrote:
You should commit with some delay between master and wicket-6.x because
otherwise wicket-examples' test
