Hi Martin,
Looks like it's fixed with the latest snapshot.
That being said, I have a weird behavior with this snapshot: if I update
the markup in Eclipse debug mode (just add a class in a class attribute for
instance, nothing fancy), I get the following exception when I reload the
page without
Hi,
There were fixes about similar problem this week.
Can you try with latest 7.0.0-SNAPSHOT?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sun, May 10, 2015 at 11:15 PM, Guillaume Smet guillaume.s...@gmail.com
wrote:
Hi,
After upgrading to Wicket 7, we
Done: https://issues.apache.org/jira/browse/WICKET-5903
Looks like it's related to optional parameters.
On Sat, May 9, 2015 at 2:39 PM, Guillaume Smet guillaume.s...@gmail.com
wrote:
Will do later today!
On Sat, May 9, 2015 at 7:12 AM, Martin Grigorov mgrigo...@apache.org
wrote:
Hi,
It
Added an entry to the new Git based wicket-site.
It will be deployed with https://issues.apache.org/jira/browse/INFRA-9559
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Apr 29, 2015 at 5:09 PM, Martin Grigorov mgrigo...@apache.org
wrote:
This is the
+1 to delete. Nice work @ all participants!
kind regards
Tobias
Am 10.05.2015 um 19:20 schrieb Andrea Del Bene an.delb...@gmail.com:
Hi,
if there are no objection I will delete the remote branches
'grails-maven-integration' and 'grails-maven-integration-6.x' as they have
Hi,
After upgrading to Wicket 7, we started to see the following exception. The
exception seems to appear only when reloading an already loaded page (ie
refresh a versioned page using the browser refresh button).
Does it ring a bell to anyone? Pointers on how to track this issue greatly
