ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Resolved: (IVY-851) Updated junit test "" unreliable/fails: unmappable character for encoding UTF8
Date Fri, 04 Jul 2008 11:01:31 GMT


Xavier Hanin resolved IVY-851.

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

I've resolved that issue by setting the encoding manually during compilation of unit tests
from our ant build file. Indeed the encoding used for the test class source is ISO-8859-1.
Maybe we should consider switching to UTF-8 as default encoding for all Ivy sources, right
now the easiest was to update the build file. 

> Updated junit test "" unreliable/fails: unmappable character
for encoding UTF8
> ------------------------------------------------------------------------------------------------------
>                 Key: IVY-851
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-RC1
>         Environment: Fedora 9; i386; Sun jdk1.5.0_15; LANG=en_US.utf8
>            Reporter: Robert Hyerle
>            Priority: Minor
>             Fix For: 2.0-RC1
> Checked out version 671603, ran "ant" with the following results:
> 1) when building, gets the following warning:
>     [javac] /home/hyerle/usr/ivy/live/ivy/test/java/org/apache/ivy/plugins/report/
warning: unmappable character for encoding UTF8
>     [javac]         String expectedOrg = "organisation=\"sp�cial\"";
>     [javac]
> 2) when running the junit tests, one gets the following failure:
>     [junit] Running
>     [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 1,626 sec
>     [junit] Test FAILED
> This is reported as:
> XML doesn't contain the organisation
> junit.framework.AssertionFailedError: XML doesn't contain the organisation
> at
> This is presumably because the mapping of the compiled string "special" (accent on the
'e') without a valid mapping does not match the contents of the test report ("test/repositories/1/special-encoding-root-ivy.xml").
> This test was checked in on 29-may as revision 661275 by gscokart.
> It is unclear to me if the test is broken for certain configurations, or only certain
LANG configurations are supported, or the original bug (IVY-816) was never completely fixed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message