Mark Derricutt wrote:
From the look of it, my guess it's because of the encoding of the
.java files.
The code reads:
convertNonASCIIString(Çüéâäàåçêë),
instead of using raw unicode references such as \uxx
When I check the file information on the source I've checked out of
CVS I see:
Even under 1.5 the tests fail, I do notice the following being logged whilst compiling thou:/home/amrk/temp/wicket/wicket/src/test/wicket/util/string/StringsTest.java:193: warning: unmappable character for encoding UTF8
convertNonASCIIString(��),and its this test that fails.However, using
On what platform are you running the tests? Linux, OSX, WinXP?
Martijn
On 12/10/05, Mark Derricutt [EMAIL PROTECTED] wrote:
Even under 1.5 the tests fail, I do notice the following being logged whilst
compiling thou:
This is an Ubuntu Breazy (Linux) machine, running Sun's Java 1.5. Under 1.5 I saw the warnings on the console for the failing test, under Mustang I didn't see the warnings but also had failing tests.
On 12/11/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
On what platform are you running the tests?
Because it is hard to reproduce... the test works on both OSX and Windows XP.
None of the core committers have linux at their disposal...
Martijn
On 12/10/05, Ingram Chen [EMAIL PROTECTED] wrote:
It had been metioned before:
If that is the only test that fails, then you can create the
distribution zip using the following maven commandline parameter:
maven -Dmaven.test.skip=true dist
Martijn
On 12/10/05, Mark Derricutt [EMAIL PROTECTED] wrote:
This is an Ubuntu Breazy (Linux) machine, running Sun's Java 1.5.
Actually, I tested that some time ago on Ubuntu mounted on VMWare.
Couldn't reproduce it there, probably due to the fact that the host OS
is WinXP.
Eelco
On 12/10/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
Because it is hard to reproduce... the test works on both OSX and Windows XP.
None
Hey all - just trying to build wicket from HEAD. First up I notice it doesn't build with maven 2 so using maven 1.I'm trying the dist goal which seems to do all its stuff, then starts running through a bunch of JUnit tests which eventually fail which leaves me without a
wicket.jar (that may be
