<build>
[...]
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.0-rc1</version>
<configuration>
<goals>install</goals>
</configuration>
</plugin>
</plugins>
[...]
</build>
On 5/30/07, Jens Hohl <[EMAIL PROTECTED]> wrote:
Ok,
the solution is to set the version of the SCM plugin, right?
How can I do that in my POM ?
SCM for worked out of the box for me ...
Thx,
Jens
-----Ursprüngliche Nachricht-----
Von: Michael Robinson [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 30. Mai 2007 20:36
An: Maven Users List
Betreff: Re: svn: error: cannot set LC_ALL locale
See JIRA:
http://jira.codehaus.org/browse/SCM-320
and a previous message on this list from just a couple of days ago (sorry
couldn't figure out how to link to the mail archives).
On 5/30/07, Jens Hohl <[EMAIL PROTECTED]> wrote:
>
>
>
> An normal SVN update works fine on my Build Maschine ..
>
> What to do with that message ?
>
>
>
> [ERROR] Provider message:
>
> [ERROR] The svn command failed.
>
> [ERROR] Command output:
>
> [ERROR] svn: error: cannot set LC_ALL locale
>
> svn: error: environment variable LANG is not set
>
> svn: error: please check that your locale name is correct
>
>
>
>
>
> thx,
>
> Jens
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
