Hi,
If i test my app by using Start.java i get the log entry
INFO - ModificationWatcher- Cannot track modifications to
resource
file:/D:/Dokumente%20und%20Einstellungen/per.n/Eigene%20Dateien/workspaces/work/whataschranz/target/classes/ch/newgro/shop/whataschranz/welcome/HomePage.html
Per,
I ran into this problem recently and solved it by removing spaces from
directory names in my project path. I plan to file a Jira issue at some
point, as it seems that ModificationWatcher should be able to handle file
paths with spaces...
-Allen
On Mon, Jan 2, 2012 at 4:42 AM, Per Newgro
Dumping the environment variables shows only these maven related variables are
set:
M2
M2_HOME
I can't see any other places where MAVEN_OPTS is being set. Nothing in maven's
settings.xml that refers to any JVM heap size options.
I noticed my version of maven is 2.2.1 dated 2009-08-07 so maybe
Well it certainly works a lot better with Maven 3.0.3! ;)
It still can't build core because of some test failures:
Running org.apache.wicket.protocol.http.StoredResponsesMapTest
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 19.351 sec
FAILURE!
Running
Thanks Allen,
that's why i was asking in list first. So if you agree i will file a
jira issue.
Per
Am 02.01.2012 18:14, schrieb Allen Gilbert:
Per,
I ran into this problem recently and solved it by removing spaces from
directory names in my project path. I plan to file a Jira issue at
Any hope this can be fixed for 1.5.4? I will hate having to change all
our modals to have a dummy call back to get it to work :(
-Nelson
On Wed, Dec 21, 2011 at 2:59 PM, Nelson Segura nsegu...@gmail.com wrote:
I have created a ticket, and attached a quick start to it
I applied the patch to my local version of 1.5.3, and it seems to
solve this issue.
On Fri, Dec 30, 2011 at 12:09 AM, northar josef.anders...@gmail.com wrote:
Yes, tested with 1.5-snapshot now (not extensively), and it seems to work. My
project manager will be glad
--
View this message in
skip the tests with -Dmaven.test.skip=true
-igor
On Mon, Jan 2, 2012 at 10:11 AM, Chris Colman
chr...@stepaheadsoftware.com wrote:
Well it certainly works a lot better with Maven 3.0.3! ;)
It still can't build core because of some test failures:
Running
a patch is welcome :)
-igor
On Mon, Jan 2, 2012 at 10:24 AM, Nelson Segura nsegu...@gmail.com wrote:
Any hope this can be fixed for 1.5.4? I will hate having to change all
our modals to have a dummy call back to get it to work :(
-Nelson
On Wed, Dec 21, 2011 at 2:59 PM, Nelson Segura
On Mon, Jan 2, 2012 at 9:47 AM, Martin Grigorov mgrigo...@apache.org wrote:
On Mon, Jan 2, 2012 at 8:18 AM, Taneli Korri tko...@gmail.com wrote:
On Sat, Dec 31, 2011 at 4:31 PM, Martin Grigorov mgrigo...@apache.org
wrote:
On Sat, Dec 31, 2011 at 2:29 PM, Taneli Korri tko...@gmail.com wrote:
Happy new year folks,
I have tomcat server running application war file serving only ajp
protocol. Apache2 is configured to serve my application using ajp. This
works - sometimes :( So far I have not able to figure out what breaks it
or what makes it work and looking for help. The description
We're running a wicket app on jetty and having an issue with signout. The app
runs on port 8443 and we have iptables redirecting from port 443. This lets
us go to https://ourap.lab without port numbers and without having the web
app run as root.
Everything is great until we do signout. We have
add the nofollow attribute to such links.
-igor
On Mon, Jan 2, 2012 at 11:05 AM, Taneli Korri tko...@gmail.com wrote:
On Mon, Jan 2, 2012 at 9:47 AM, Martin Grigorov mgrigo...@apache.org wrote:
On Mon, Jan 2, 2012 at 8:18 AM, Taneli Korri tko...@gmail.com wrote:
On Sat, Dec 31, 2011 at 4:31
:) A patch will be nice, but ... I think this has to do with my modal
window using page instead of panel. Could it be?
The window clears up the shown flag correctly if I press in the x
for the modal window, because the CloseButtonBehavior gets called, but
then the Ajax Target being used is in the
On 01/03/2012 12:30 AM, Nelson Segura wrote:
The shown flag is set up to false by window.close(), but it stays as true
in the
context of the parent page. This prevents the page from being opened a
second time. Maybe something similar to how you cannot pass pages
directly to a modal, but
I noticed also that if I add a dummy window closed call back to my page:
1) In the modal window, calling window.close() sets the shown flag to false
2) My dummy callback causes ModalWindow.WindowClosedBehavior to
respond. The current value of this shown flag is still true! Then the
behavior sets
Greetings all,
I've run into some trouble using RestartResponseAtInterceptPageException since
moving from Wicket 1.4.13 to 1.5.3. The flow I'm implementing is a login via
an OAuth service, so the user is redirected by way of RedirectPage to the OAuth
provider and eventually ends up back at my
Hi,
This behavior is by design.
I cannot say why AccessDeniedException is being thrown without
debugging it but I can suggest you to try:
LoginLink {
onClick() {
if (notLoggedIn) {
throw new RestartResponseAtInterceptPageException(new
RedirectPage(getOAuthUrl()));
}
}
On Tue, Jan 3,
18 matches
Mail list logo
