Yep. Maybe you're right.
On Sun, May 8, 2011 at 12:06 PM, Juergen Donnerstag
wrote:
> I think we should strive to avoid telling users they have to set up
> their IDE in a specific way. Instead I'd suggest to replace £ with
> \u00A3. That should work everywhere irrespective of any IDE or OS
> sett
I think we should strive to avoid telling users they have to set up
their IDE in a specific way. Instead I'd suggest to replace £ with
\u00A3. That should work everywhere irrespective of any IDE or OS
setting.
On Sun, May 8, 2011 at 11:46 AM, Martin Grigorov wrote:
> The code actually looks like
The code actually looks like:
assertTrue("One of the pound entity representations is missing:
£ or £",
response.contains("££"));
i.e. "££" seems to be broken by your ide.
See at
http://svn.apache.org/viewvc/wicket/trunk/wicket-core/src/test/java/org/apache/wicket/markup/
The *root* cause seems to be obvious. Instead of changing any eclipse
settings, the assert statement must be changed. Replace "££" with a
properly encoded unicode \u
Juergen
On Sun, May 8, 2011 at 11:24 AM, Martin Grigorov wrote:
> My Eclipse uses en_US locale and all is fine.
> My Maven s
My Eclipse uses en_US locale and all is fine.
My Maven setup uses bg_BG and again all is fine. Just verified.
Igor mentioned that this test started to fail at his machine
yesterday, but I guess his setup completely is en_US.
On Sun, May 8, 2011 at 11:13 AM, Juergen Donnerstag
wrote:
> Hi,
>
> on
On Sun, 8 May 2011 11:13:27 +0200
Juergen Donnerstag wrote:
> The assertion test is like: response.contains("££")); replacing it
> with response.contains("\u00A3\u00A3")); works for me.
It's loading UTF-8 data but interprets it as probably ISO-8859-1.
> Interestingly it's failing in eclipse
Hi,
on my (german) laptop testComponentAttributesNotDoubleEscaped is failing.
junit.framework.AssertionFailedError: One of the pound entity
representations is missing: £ or £
at
org.apache.wicket.markup.ComponentTagAttributeEscapingTest.testComponentAttributesNotDoubleEscaped(ComponentTa
