Does any one know why this just started to happen? Did the SCM plugin change? I have been using 2.0.4 since Nov 2006. Do I need to upgrade or is there a setting I need to re-config.....
On 5/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
so after I set LANG to en_US, I still get the error: css-paps01:->setenv LANG en_US [INFO] [scm:update] [INFO] Executing: svn --non-interactive update [INFO] Working directory: /usr2/local/builds/CSS_JAVA_DEV/projects [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] couldn't set locale correctly couldn't set locale correctly svn: error: cannot set LC_ALL locale svn: error: environment variable LANG is en_US svn: error: please check that your locale name is correct On 5/29/07, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > I have the locale settings but I still have the errors. Also, I am using > cshell so I hope setenv is doing the same things as export. > > css-paps01:->locale -a > C > POSIX > en_CA > en_CA.ISO8859-1 > en_US > en_US.ISO8859-1 > en_US.ISO8859-15 > [EMAIL PROTECTED] > en_US.UTF-8 > es > es.UTF-8 > es_MX > es_MX.ISO8859-1 > fr > fr.UTF-8 > fr_CA > fr_CA.ISO8859-1 > iso_8859_1 > ja > ja_JP.PCK > > > On 5/29/07, Heinrich Nirschl <[EMAIL PROTECTED]> wrote: > > > > I think the error messages are written by svn because the en_US.UTF-8 > > locale does not exist on the machine. I can reproduce the errors if I > > try svn with a non-existing locale (en_GB does not exist on my box): > > > > $ LANG=en_GB svn st > > svn: error: cannot set LC_ALL locale > > svn: error: environment variable LANG is en_GB > > svn: error: please check that your locale name is correct > > > > To check which locales are available the command > > > > $ locale -a > > > > can be used. > > > > - Henry > > > > On Tue, 2007-05-29 at 18:34 +0200, Emmanuel Venisse wrote: > > > LC_MESSAGE=en_EN is set by default in this version because maven-scm > > can't parse messages that aren't in english. > > > > > > Do you have already set LC_ALL? > > > Maybe it will work if you set LANG to en_EN > > > > > > Emmanuel > > > > > > Owen Jacobson a écrit : > > > > It is 2.0-beta-6; will that solution still apply? > > > > > > > > Owen > > > > > > > > On 5/28/07, Emmanuel Venisse <[EMAIL PROTECTED] > wrote: > > > >> What is your release plugin version? > > > >> > > > >> If it isn't 2.0-bate-6, you can try to set LC_MESSAGES to en_EN > > > >> > > > >> Emmanuel > > > >> > > > >> Owen Jacobson a écrit : > > > >> > Good afternoon. > > > >> > > > > >> > I recently upgraded from Maven 2.0.4 to 2.0.6. At about the > > same > > > >> > time, the maven-release-plugin stopped working with subversion > > SCM > > > >> > configurations. > > > >> > > > > >> > When I try to run release:prepare, I get the following: > > > >> > > > > >> > [INFO] Executing: svn --non-interactive status > > > >> > [INFO] Working directory: /home/ojacobson/admin-parent > > > >> > [INFO] > > > >> > > > > >> > > ------------------------------------------------------------------------ > > > >> > [ERROR] BUILD FAILURE > > > >> > [INFO] > > > >> > > > > >> > > ------------------------------------------------------------------------ > > > >> > [INFO] Unable to check for local modifications > > > >> > Provider message: > > > >> > The svn command failed. > > > >> > Command output: > > > >> > svn: error: cannot set LC_ALL locale > > > >> > svn: error: environment variable LANG is en_US.UTF-8 > > > >> > svn: error: please check that your locale name is correct > > > >> > > > > >> > However, if I run > > > >> > $ cd /home/ojacobson/admin-parent > > > >> > $ svn --non-interactive status > > > >> > myself, I get a normal, successful svn stat listing. > > > >> > > > > >> > The subversion guys are stumped; anyone from the maven side > > have any > > > >> > suggestions? > > > >> > > > > >> > Owen > > > >> > > > > >> > > > --------------------------------------------------------------------- > > > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> > For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > > >> > > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > >> > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
