I've discovered one solution that worked for me.
I don't know if I have a different problem than was mentioned here, but it
was the same error.
I did have the same issues mentioned in this thread and tried all sorts of
subversion client's.
Try fixing the scm configuration first to point to the co
I'm forced to go with 1.5.1 right now, so here is a workaround that worked
for me (on gentoo):
* Checkout a working copy with svn client 1.5.1, otherwise svn copy fails
with file already exists
* run mvn release:prepare, it will fail in the svn --non-interactive copy
...
* run svn update
* ru
m running
> into the same problem as you.
>
> Stephen refered to similar issues today in this list.
>
> Regards
> Stefan
>
>
> -Ursprüngliche Nachricht-
> Von: David Roussel [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 26. August 2008 16:39
> An: users@
. August 2008 16:39
An: users@maven.apache.org
Betreff: Re: AW: Release fails during SVN commit
Stefan,
If it works for you, is it because it's a single module with no nested
modules?
I have maven 2.0.9, svn 1.5.1 (trigis.org build), Java 1.6.0_06, Windows XP
SP2,
It's interesting that t
Stefan,
If it works for you, is it because it's a single module with no nested
modules?
I have maven 2.0.9, svn 1.5.1 (trigis.org build), Java 1.6.0_06, Windows XP
SP2,
It's interesting that the command that fails:
svn --non-interactive copy --file
C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm
Hi Andreas,
I am not sure but maybe this would be worth a try.
In my projects I always refer to the trunk folder in the SCM configuration and
point to the tags or releases folder in the tagBase property of the
maven-release-plugin.
So your configuration would look like this in your pom.xml:
Users List
Subject: RE: AW: Release fails during SVN commit
I use Windows Vista SP1, Sun JDK 5u16, Maven 2.0.9 and SVN 1.5.1 (built by
SlikSVN [1]) and an SVN HTTP-based Server at 1.5.1, and have performed two
releases recently with no issues.
[1] http://www.sliksvn.com/en/download
PROTECTED]
Sent: Thursday, August 21, 2008 1:43 PM
To: 'Maven Users List'
Subject: AW: AW: Release fails during SVN commit
As the discussion pointed by Emmanuel shows the root of the problem is the SVN
1.5.1 client software. I can't say if it is a bug or a changed behaviour, refer
to
time.
-Andreas.
-Ursprüngliche Nachricht-
Von: Stephen Duncan Jr [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 16:46
An: Maven Users List
Betreff: Re: AW: Release fails during SVN commit
If it's happening directly from the command-line as Daniel indicated (I
haven't tried
Hi Nathan,
no there are no keyword substitutions. It seems to be a SVN bug, or changed
behaviour maybe.
-Andreas.
-Ursprüngliche Nachricht-
Von: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 17:07
An: Maven Users List
Betreff: RE: Release fails during SVN
Yes, maven-scm use the command line.
I extracted the JavaHL comment from the thread on the svn users list, and I
don't know if some other part was impacted with this change
Emmanuel
On Thu, Aug 21, 2008 at 4:45 PM, Stephen Duncan Jr <[EMAIL PROTECTED]
> wrote:
> If it's happening directly from t
If it's happening directly from the command-line as Daniel indicated (I
haven't tried it myself, but as far as I know Maven uses the command-line,
not JavaHL), then it can't be a JavaHL issue.
-Stephen
On Thu, Aug 21, 2008 at 10:38 AM, Emmanuel Venisse <
[EMAIL PROTECTED]> wrote:
> The issue is
The issue is discussed on the subversion users list :
http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html
It is related to a change in JavaHL:
* correctly set the peg revision for copy in JavaHL (r31994)
Emmanuel
On Thu, Aug 21, 2008 at 4:15 PM, Daniel Kulp <[EMAIL PR
On Thursday 21 August 2008 10:09:07 am Stephen Duncan Jr wrote:
> On the other hand, the fact that I forgot to run svn up before running the
> release plugin has bitten me before, and I had to make a second release
> because I didn't realize it. Ideally it'd warn you about remote changes
> the sam
On the other hand, the fact that I forgot to run svn up before running the
release plugin has bitten me before, and I had to make a second release
because I didn't realize it. Ideally it'd warn you about remote changes the
same way it does about local uncommitted changes. But that still leaves th
I had the same problem with 1.5.1 on Gentoo.It's a subversion problem, not
a release plugin problem.If you run the same command that release is
trying to run (can be seen when you run mvn with -X), it fails. Basically,
with 1.5, you apparently cannot "svn cp" your working copy into a
Hi Stephen,
thank you for your answer.
Can anyone else confirm this? So one (probably me) should report this issue at
the issue tracker.
Andreas.
-Ursprüngliche Nachricht-
Von: Stephen Duncan Jr [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 14:48
An: Maven Users List
No, we use MS Windows Vista, and XP. The problem occurs on each of these
platforms.
-Ursprüngliche Nachricht-
Von: Luke Daley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 21. August 2008 11:12
An: Maven Users List
Betreff: Re: Release fails during SVN commit
If your on Mac OS 10.5, ch
18 matches
Mail list logo
