On Thu, Jul 14, 2011 at 1:22 PM, Matt Brictson wrote:
> Hmm. I would expect that your LoginPage would see changes reflected when you
> hit the browser refresh button. Sounds like a bug to me.
>
> Is it related to this one?
>
> https://issues.apache.org/jira/browse/WICKET-3891
This bug says that
On Wed, Jul 13, 2011 at 2:40 PM, Matt Brictson wrote:
> FWIW I tried 1.5-SNAPSHOT and the HTML resource reloading seems to work fine.
I'm seeing reloading working as expected on the basic HomePage.
However, on a LoginPage that I'm working on, a I do not see changes
reflected until I go to the URL
With the latest snapshot, I still wasn't seeing changes propagate. Until --
On Wed, Jul 13, 2011 at 2:03 PM, Martin Grigorov wrote:
> It is possible but you have to extend maven-jetty-plugin's configuration.
> There was something about Scanner. Ask Google for more info
Adding the scanIntervalSec
> 'Resources in the
> htmlDir that was already set, like CSS, are also not updating.
I apologize for sending that last message prematurely; things in the
webapp/ directory are updating. HTML in the java/ subfolder is not,
however.
--
On Wed, Jul 13, 2011 at 1:04 PM, Matt Brictson wrote:
> The way I've always done it (and this works just fine outside of Eclipse as
> well), is to enable resource polling in Wicket for the directory that
> contains the HTML files.
>
> In the init() method of your WebApplication subclass (in the
Hello,
I'm investigating writing a new project in Wicket and am playing
around with a project created from the 1.5-RC5.1 quickstart maven
archetype.
Using 'mvn jetty:run' from the command-line, none of the changes I
make to source files, either Java or HTML, are picked up unless I
restart the ser
