You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Gilles Scokart (JIRA)" <ji...@apache.org> on 2006/12/05 07:51:26 UTC
[jira] Commented: (IVY-346) Ivy failure when the ivy.xml file
contains non US-ASCII characters
[ http://issues.apache.org/jira/browse/IVY-346?page=comments#action_12455535 ]
Gilles Scokart commented on IVY-346:
------------------------------------
Don't apply the patch too quickly. I just realized that some unit tests have to be updated as well. The patch as it is here will indeed broke some unit tests ( UTF-8 must be added in the prolog of the expected files).
I'm working on it. I will post a new patch soon.
> Ivy failure when the ivy.xml file contains non US-ASCII characters
> ------------------------------------------------------------------
>
> Key: IVY-346
> URL: http://issues.apache.org/jira/browse/IVY-346
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Gilles Scokart
> Priority: Critical
> Attachments: ivy-346.patch
>
>
> If we have an ivy file containing non US-ASCII charcters in an UTF-8 encoding, you make a resolved and then a publish, you receive an exception like this :
> build_base.xml:203: impossible to publish artifacts for [ XXXX | core | working@XXXX ]: impossible to deliver [ XXXX | core | working@XXXX ]: java.lang.IllegalStateException: bad ivy file in cache for [ XXXX | core | working@XXXX ]: please clean and resolve again
> Note that the special characters might be in XML comments also.
> The errors come from the fact that the resolved-XXX-core-working@XXXX.xml placed in the case is written with the local encoding instead of the UTF-8 (or the original) encoding.
> The workaround is to clean the cache and remove the special characters from the original ivy file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira