svn checkout - special characters in file name are not encoding properly

There is not sufficient information to reproduce/analyze the issue, please re-open with a demo project showing the issue.

"modŠle fields-replacements.xsl" (S with caron) is the file name in subversion repository

after using the below mentioned pom.xml to checkout the project,
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<dependencies>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-antlr</artifactId>
<version>1.6.5</version>
</dependency>
</dependencies>
<executions>
<execution>
<phase>process-resources</phase>
<configuration>
<tasks>
<path id="project.classpath">
<pathelement location="$

/svnant.jar" />
<pathelement location="$

/svnjavahl.jar" />
<pathelement location="$

/svnkit.jar" />
</path>
<taskdef name="svn" classname="org.tigris.subversion.svnant.SvnTask" classpathref="project.classpath"/>
<svn username="svn" password="svn">
<checkout url="svn://10.192.27.65/home/svn/iVision3.3_SVNRepo_07072010/branches/$

/$

"/>
</svn>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>

the file name is coming as "mod?le fields-replacements.xsl"

The special character(S with caron) in origin file name is getting dissappeared.

Please help me to get out of this issue.

Highly appreciated for the quick response.

Thank you

Regards,
Sunny

Maven isn't responsible for the SVN checkout, this is an issue with a third-party tool, Subversion in this case. Please contact the Subversion support or try different means to do the checkout like using the maven-scm-plugin.

The same thing when I'm trying to checking out with the using of command line, the file name is coming properly, but with the using of maven only it is giving the problem.

The maven svn checkout is giving the problem.
Please help me out to solve this issue.

I feel glad for immediate response!!!

Thank you...

Can you paste the output of "mvn -version"? It will print Java's system locale and encoding. Additionally provide the value of the LANG environment variable from the command line you're calling Maven (using "echo $LANG") and all other environment variables starting with "LC_".

Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530)
Java version: 1.5.0
Java home: /usr/java5_64/jre
Default locale: en_US, platform encoding: ISO8859-1
OS name: "aix" version: "5.3" arch: "ppc64" Family: "unix"

LANG envoronment variable is: en_US

Please suggest me where can I find remaining environment variables in maven.

Thanks,
Sunny

Well, this info already exposes the problem. You run Java with ISO-8859-1, but the file names in subversion contain characters that have no equivalent in this encoding. Can you also paste what output the command "locale" and "locale -a" produces?

Please find the below results for "locale" and "locale -a"
----------------------------------------------------------

svnuser@MUMSA00100260:/home/svnuser]locale
LANG=en_US
LC_COLLATE="en_US"
LC_CTYPE="en_US"
LC_MONETARY="en_US"
LC_NUMERIC="en_US"
LC_TIME="en_US"
LC_MESSAGES="en_US"
LC_ALL=
svnuser@MUMSA00100260:/home/svnuser]locale -a
C
POSIX
sbcs.imcompose
en_US
en_US.8859-15
en_US.ISO8859-1
en_US.8859-15.imkeymap
en_US.ISO8859-1.imkeymap
en_US.ISO8859-1.lftkeymap
en_US.ISO8859-1@alt.lftkeymap
en_US.8859-15@alt.imkeymap
en_US.imkeymap
en_US@alt.imkeymap
en_US.ISO8859-1@alt.imkeymap
en_US.imcompose
en_US@alt.imcompose
en_US.ISO8859-1.imcompose
en_US.ISO8859-1@alt.imcompose
en_US.8859-15.imcompose
en_US.8859-15@alt.imcompose
en_US.lftkeymap
en_US@alt.lftkeymap
svnuser@MUMSA00100260:/home/svnuser]

Regards,
Sunny

<taskdef name="svn" classname="org.tigris.subversion.svnant.SvnTask" classpathref="project.classpath"/>

This is the component doing the checkout, and this is not Maven. It runs in the context of a Maven build but that doesn't make Maven responsible for the misbehavior of this component, just like a misbehaving Java application is not a bug of the JVM. For getting qualified help, it's important to address the community maintaining the affected component (SVN Ant Task).

You can freely continue your discussion here but the Maven core cannot help you solve your issue with third-party tools.

In addition to Benjamin's answer, you should also read http://www.sunsource.net/scdocs/SVNEncoding and really reconsider strongly the necessity for such file names in Subversion at all.

You might want to try and contact http://subclipse.tigris.org/servlets/ProjectProcess?pageID=t65B1R instead.

It's as Benjamin said, I have also no clue what the SVN Ant task really does in terms of code. If the native svn client is able to handle the characters it just means that it makes right assumptions about the encoding used by the svn client that created these subversion entries in first place. But as the provided link explains, there is no standard enforced by subversion itself and it also seems to imply that it does make a difference if you use a native svn client provided by Collabnet or someone else. There's even a Java implementation of the SVN protocol (SVNKit) that might be used by the SVN Ant task. Your error simply indicates that the client used by the SVN Ant task is not compatible and it is no wonder if it is Java based looking at the encoding in use. However, only the people that created this SVN Ant Task can tell you more, Maven is simply an ordinary consumer of that 3rd party code and not responsible for its malfunction. You have to follow Benjamin's advice and ask in their community or follow mine not to use such file names in a repository that cannot really handle it by design.

Thank you Benjamin and Jeorg. I'll post the JIRA in SVNAnt blog.

Thanks for your time.