You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guimiot Isabelle (JIRA)" <ji...@codehaus.org> on 2008/03/26 12:12:58 UTC

[jira] Created: (MCHANGELOG-83) avoid a build fail when there are specific characters in a filename

avoid a build fail when there are specific characters in a filename
-------------------------------------------------------------------

                 Key: MCHANGELOG-83
                 URL: http://jira.codehaus.org/browse/MCHANGELOG-83
             Project: Maven 2.x Changelog Plugin
          Issue Type: Bug
    Affects Versions: 2.1
         Environment: Windows/Linux , maven 2.0.8
            Reporter: Guimiot Isabelle
            Priority: Minor


When I commit a file from a windows platform on CVS, with a name containing specific characters (for example :  "schéma.xml", containing character "é"), the "cvs log" command is ok on windows (iso-8859-1) and  it contains just some "warning line" on linux (utf-8) which says "cvs server: nothing known about sch?ma.xml". This warning line doesn't make the cvs log command fail, I have all the information I need about every file that changed during the last month...

When I run the changelog:changelog goal, if I run maven with "MAVEN_OPTS=-Dfile.encoding=ISO-8859-1" (JVM option), everything's ok, but if I run the same goal with "MAVEN_OPTS=-Dfile.encoding=UTF-8", the warning line that I could read on linux ("nothing known about...") makes my whole build fail ! 


[ERROR] Provider message:
[ERROR] The cvs command failed.
[ERROR] Command output:
[ERROR] cvs server: nothing known about sch&#65533;ma.xml
 
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error has occurred in Change Log report generation.

Embedded error: An error has occurred during changelog command : 
Command failed.



Could you resolve this problem with some cvs error parsing that could detect what king of error is serious, and what kind of error is just a small warning ?

many thanks !

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira