You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Andreas Heinecke <an...@objectinc.de> on 2008/08/21 10:04:06 UTC

Release fails during SVN commit

Hi there,

I encountered a strange problem. Since a few weeks I'm not able to perform a
release with Maven. The release process fails during executing the
release:prepare goal at the same position, always. The point at which the
release fails is when Maven tries to commit the release POM's to SVN. This
commit fails with the error message that the file which is about to be
committed already exists at the position in SVN. But it isn't there.
Strange, uh?

I actually checked the tagbase configuration of the plugin and tried to
alter it, but the effect remains.
I don't know what I can try to fix this issue.
The last thing altered at the configuration is a switch of the SVN server.
We had to switch to a newer SVN version 1.5.0. We also switched to the new
1.5.0 SVN client as we know that there are problems with newer server
software and older client software.

Please find parts of my pom.xml configuration attached below.

Any pointers are welcome.

Regards,
Andreas.

My SCM configuration:
<scm>
    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>
 
<developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
rConnection>
    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
</scm>

My release plugin configuration:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <configuration>
        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
        <autoVersionSubmodules>true</autoVersionSubmodules>
        <preparationGoals>clean install</preparationGoals>
    </configuration>
</plugin>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Release fails during SVN commit

Posted by Arnaud HERITIER <ah...@gmail.com>.

I have the same issue on Leopard with svn 1.5
As a workaround I have to checkout the trunk of the project just before to
do the release and it works.

Arnaud

On Thu, Aug 21, 2008 at 5:07 PM, Beyer,Nathan <NB...@cerner.com> wrote:

> Does your POM have any SVN keyword substitutions in it? For example "$Id$"
> or "$Revision$"? I have had issues with releases that at the root was a file
> locking problem that I was able to alleviate by removing the keywords
> substitutions.
>
> -Nathan
>
> -----Original Message-----
> From: Andreas Heinecke [mailto:andreas@objectinc.de]
> Sent: Thursday, August 21, 2008 3:04 AM
> To: users@maven.apache.org
> Subject: Release fails during SVN commit
>
> Hi there,
>
> I encountered a strange problem. Since a few weeks I'm not able to perform
> a
> release with Maven. The release process fails during executing the
> release:prepare goal at the same position, always. The point at which the
> release fails is when Maven tries to commit the release POM's to SVN. This
> commit fails with the error message that the file which is about to be
> committed already exists at the position in SVN. But it isn't there.
> Strange, uh?
>
> I actually checked the tagbase configuration of the plugin and tried to
> alter it, but the effect remains.
> I don't know what I can try to fix this issue.
> The last thing altered at the configuration is a switch of the SVN server.
> We had to switch to a newer SVN version 1.5.0. We also switched to the new
> 1.5.0 SVN client as we know that there are problems with newer server
> software and older client software.
>
> Please find parts of my pom.xml configuration attached below.
>
> Any pointers are welcome.
>
> Regards,
> Andreas.
>
> My SCM configuration:
> <scm>
>    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>
>
> <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project
> </develope
> rConnection>
>    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> </scm>
>
> My release plugin configuration:
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-release-plugin</artifactId>
>    <configuration>
>        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>        <autoVersionSubmodules>true</autoVersionSubmodules>
>        <preparationGoals>clean install</preparationGoals>
>    </configuration>
> </plugin>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> ----------------------------------------------------------------------
> CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

AW: Release fails during SVN commit

Posted by Andreas Heinecke <an...@objectinc.de>.

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:NBEYER@CERNER.COM] 
Gesendet: Donnerstag, 21. August 2008 17:07
An: Maven Users List
Betreff: RE: Release fails during SVN commit

Does your POM have any SVN keyword substitutions in it? For example "$Id$"
or "$Revision$"? I have had issues with releases that at the root was a file
locking problem that I was able to alleviate by removing the keywords
substitutions.

-Nathan

-----Original Message-----
From: Andreas Heinecke [mailto:andreas@objectinc.de] 
Sent: Thursday, August 21, 2008 3:04 AM
To: users@maven.apache.org
Subject: Release fails during SVN commit

Hi there,

I encountered a strange problem. Since a few weeks I'm not able to perform a
release with Maven. The release process fails during executing the
release:prepare goal at the same position, always. The point at which the
release fails is when Maven tries to commit the release POM's to SVN. This
commit fails with the error message that the file which is about to be
committed already exists at the position in SVN. But it isn't there.
Strange, uh?

I actually checked the tagbase configuration of the plugin and tried to
alter it, but the effect remains.
I don't know what I can try to fix this issue.
The last thing altered at the configuration is a switch of the SVN server.
We had to switch to a newer SVN version 1.5.0. We also switched to the new
1.5.0 SVN client as we know that there are problems with newer server
software and older client software.

Please find parts of my pom.xml configuration attached below.

Any pointers are welcome.

Regards,
Andreas.

My SCM configuration:
<scm>
    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>
 
<developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
rConnection>
    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
</scm>

My release plugin configuration:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <configuration>
        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
        <autoVersionSubmodules>true</autoVersionSubmodules>
        <preparationGoals>clean install</preparationGoals>
    </configuration>
</plugin>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

----------------------------------------------------------------------
CONFIDENTIALITY NOTICE This message and any included attachments are from
Cerner Corporation and are intended only for the addressee. The information
contained in this message is confidential and may constitute inside or
non-public information under international, federal, or state securities
laws. Unauthorized forwarding, printing, copying, distribution, or use of
such information is strictly prohibited and may be unlawful. If you are not
the addressee, please promptly delete this message and notify the sender of
the delivery error by e-mail or you may call Cerner's corporate offices in
Kansas City, Missouri, U.S.A at (+1) (816)221-1024.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Release fails during SVN commit

Posted by "Beyer,Nathan" <NB...@CERNER.COM>.

Does your POM have any SVN keyword substitutions in it? For example "$Id$" or "$Revision$"? I have had issues with releases that at the root was a file locking problem that I was able to alleviate by removing the keywords substitutions.

-Nathan

-----Original Message-----
From: Andreas Heinecke [mailto:andreas@objectinc.de] 
Sent: Thursday, August 21, 2008 3:04 AM
To: users@maven.apache.org
Subject: Release fails during SVN commit

Hi there,

I encountered a strange problem. Since a few weeks I'm not able to perform a
release with Maven. The release process fails during executing the
release:prepare goal at the same position, always. The point at which the
release fails is when Maven tries to commit the release POM's to SVN. This
commit fails with the error message that the file which is about to be
committed already exists at the position in SVN. But it isn't there.
Strange, uh?

I actually checked the tagbase configuration of the plugin and tried to
alter it, but the effect remains.
I don't know what I can try to fix this issue.
The last thing altered at the configuration is a switch of the SVN server.
We had to switch to a newer SVN version 1.5.0. We also switched to the new
1.5.0 SVN client as we know that there are problems with newer server
software and older client software.

Please find parts of my pom.xml configuration attached below.

Any pointers are welcome.

Regards,
Andreas.

My SCM configuration:
<scm>
    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>

<developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
rConnection>
    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
</scm>

My release plugin configuration:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <configuration>
        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
        <autoVersionSubmodules>true</autoVersionSubmodules>
        <preparationGoals>clean install</preparationGoals>
    </configuration>
</plugin>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

----------------------------------------------------------------------
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Release fails during SVN commit

Posted by "Sommers, Elizabeth" <So...@Pragmatics.com>.

Some of my users are having the same problem.  I think it has to do with
the svn 1.5 client. 

Liz Sommers
sommerse@pragmatics.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven and Eclipse Project

Posted by Eugene Kuleshov <eu...@md.pp.ru>.

Michael McCallum-3 wrote:
> 
>> maybe you want to look into this:  http://code.google.com/p/mvnlink/
>> it sounds like it does what you're looking for.
> use the m2eclipse.codehaus.org plugin and then run mvn eclipse:m2eclipse
> 

If you are using m2eclipse, I wouldn't recommend using eclipse:m2eclipse.
Instead use one of the project import wizards provided by m2eclipse. They
allow to import multiple projects from local system, checkout from SCM or
import by Maven coordinates. See http://tinyurl.com/5qzyzx

  This way project interdependencies and configuration for other Eclipse
tools, such as AJDT or WTP will be done automatically. See for example WTP
howto. http://tinyurl.com/5zoawl

Michael McCallum-3 wrote:
> 
> far better solution... there is one caveat make sure that maven and
> eclipse 
> have different output folders... eclipse generates class are not meant to
> be 
> packaged up...
> 

  Because of several issues with option for using separate output folders
between Eclipse and Maven CLI, we had to remove it in m2eclipse 0.9.5. If
you are not jumping back and forth between Eclipse and command line it works
much better for the IDE and the only caveat is that you need to not forget
to perform Refresh and Project / Clean after you done something with the
project outside IDE.
  We are still looking at better solution for this issue. In a mean time, if
you prefer to use separate output folders, you can do that with a custom
profile. See more details at
http://tinyurl.com/373bkh#ProjectFAQ-outputFolders  

  regards,
  Eugene

-- 
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19108305.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven and Eclipse Project

Posted by Michael McCallum <gh...@apache.org>.

On Fri, 22 Aug 2008 08:28:36 Andrew Close wrote:
> On Thu, Aug 21, 2008 at 9:51 AM, Lam Hayward <Ha...@lac-bac.gc.ca> 
wrote:
> > Hi there,
> >
> > I have an issue with maven classpath generation ("mvn eclipse:eclipse")
> > for eclipse.
> >
> > I have 3 independent projects (say A, B and C) with no common root.
> > Project A is the common project (jar) which project B and C will
> > include.
> >
> > In pom.xml in project B and project C, there is a dependency defined for
> > A. However, in eclipse, I'd like to have project B and project C to
> > include the project A as reference project instead of the jar.
> >
> > Is this possible without using the project hierarchy approach?
>
> maybe you want to look into this:  http://code.google.com/p/mvnlink/
> it sounds like it does what you're looking for.
use the m2eclipse.codehaus.org plugin and then run mvn eclipse:m2eclipse

far better solution... there is one caveat make sure that maven and eclipse 
have different output folders... eclipse generates class are not meant to be 
packaged up...


-- 
Michael McCallum
Enterprise Engineer
mailto:gholam@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven and Eclipse Project

Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.

I installed the eclipse plugin from
http://mvnlink.googlecode.com/svn/mvnlink-update-site/ and restarted
eclipse. According to the project page, some top level menu should have
MvnLink, there is no none. Is there some configuration I am missing? 

-----Original Message-----
From: Andrew Close [mailto:aclose@gmail.com] 
Sent: August 21, 2008 4:29 PM
To: Maven Users List
Subject: Re: Maven and Eclipse Project

On Thu, Aug 21, 2008 at 9:51 AM, Lam Hayward <Ha...@lac-bac.gc.ca>
wrote:
> Hi there,
>
> I have an issue with maven classpath generation ("mvn 
> eclipse:eclipse") for eclipse.
>
> I have 3 independent projects (say A, B and C) with no common root.
> Project A is the common project (jar) which project B and C will 
> include.
>
> In pom.xml in project B and project C, there is a dependency defined 
> for A. However, in eclipse, I'd like to have project B and project C 
> to include the project A as reference project instead of the jar.
>
> Is this possible without using the project hierarchy approach?

maybe you want to look into this:  http://code.google.com/p/mvnlink/ it
sounds like it does what you're looking for.

--
Andrew Close

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven and Eclipse Project

Posted by Andrew Close <ac...@gmail.com>.

On Thu, Aug 21, 2008 at 9:51 AM, Lam Hayward <Ha...@lac-bac.gc.ca> wrote:
> Hi there,
>
> I have an issue with maven classpath generation ("mvn eclipse:eclipse")
> for eclipse.
>
> I have 3 independent projects (say A, B and C) with no common root.
> Project A is the common project (jar) which project B and C will
> include.
>
> In pom.xml in project B and project C, there is a dependency defined for
> A. However, in eclipse, I'd like to have project B and project C to
> include the project A as reference project instead of the jar.
>
> Is this possible without using the project hierarchy approach?

maybe you want to look into this:  http://code.google.com/p/mvnlink/
it sounds like it does what you're looking for.

-- 
Andrew Close

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven and Eclipse Project

Posted by Eugene Kuleshov <eu...@md.pp.ru>.


  Out of curiosity, why don't you give a try to m2eclipse?
http://m2eclipse.codehaus.org/

  among lot of other things, it would automatically handle project import
for you and will configure imported projects for other Eclipse tools.

  regards,
  Eugene



Lam Hayward wrote:
> 
> Thanks for the suggestion.
> 
> It does not work. No error reported. The build path still does not show
> any project dependency. 
> 
> -----Original Message-----
> From: Wayne Fay 
> Sent: August 21, 2008 3:40 PM
> To: Maven Users List
> Subject: Re: Maven and Eclipse Project
> 
> You need to configure the eclipse plugin as Arnaud said:
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
> 
> It will be something like:
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-eclipse-plugin</artifactId>
>         <configuration>
>           <workspace>...</workspace>
>         </configuration>
>       </plugin>
> 
> Wayne
> 

-- 
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19108349.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven and Eclipse Project

Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.

Thanks for the suggestion.

It does not work. No error reported. The build path still does not show
any project dependency. 

-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com] 
Sent: August 21, 2008 3:40 PM
To: Maven Users List
Subject: Re: Maven and Eclipse Project

You need to configure the eclipse plugin as Arnaud said:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html

It will be something like:
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-eclipse-plugin</artifactId>
        <configuration>
          <workspace>...</workspace>
        </configuration>
      </plugin>

Wayne

On 8/21/08, Lam Hayward <Ha...@lac-bac.gc.ca> wrote:
> I tried setting the following properties in pom.xml or command line:
>
> workspace
> eclipse.workspace
> maven.eclipse.workspace
>
> The command does not report any error. However, the eclipse buildpath 
> of project B or project C still do not reference project A.
>
> Any idea?
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: August 21, 2008 1:55 PM
> To: Maven Users List
> Subject: Re: Maven and Eclipse Project
>
> using the workspace property the eclipse plugin can find references to

> others projects and link them.
> Otherwise without having an inheritence but a reactor pom with 3 
> modules will also link them together.
>
> On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>wrote:
>
> > Hi there,
> >
> > I have an issue with maven classpath generation ("mvn
> > eclipse:eclipse") for eclipse.
> >
> > I have 3 independent projects (say A, B and C) with no common root.
> > Project A is the common project (jar) which project B and C will 
> > include.
> >
> > In pom.xml in project B and project C, there is a dependency defined

> > for A. However, in eclipse, I'd like to have project B and project C

> > to include the project A as reference project instead of the jar.
> >
> > Is this possible without using the project hierarchy approach?
> >
> > HL
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com www.octo.com | 
> blog.octo.com
..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven and Eclipse Project

Posted by Wayne Fay <wa...@gmail.com>.

You need to configure the eclipse plugin as Arnaud said:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html

It will be something like:
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-eclipse-plugin</artifactId>
        <configuration>
          <workspace>...</workspace>
        </configuration>
      </plugin>

Wayne

On 8/21/08, Lam Hayward <Ha...@lac-bac.gc.ca> wrote:
> I tried setting the following properties in pom.xml or command line:
>
> workspace
> eclipse.workspace
> maven.eclipse.workspace
>
> The command does not report any error. However, the eclipse buildpath of
> project B or project C still do not reference project A.
>
> Any idea?
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: August 21, 2008 1:55 PM
> To: Maven Users List
> Subject: Re: Maven and Eclipse Project
>
> using the workspace property the eclipse plugin can find references to
> others projects and link them.
> Otherwise without having an inheritence but a reactor pom with 3 modules
> will also link them together.
>
> On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward
> <Ha...@lac-bac.gc.ca>wrote:
>
> > Hi there,
> >
> > I have an issue with maven classpath generation ("mvn
> > eclipse:eclipse") for eclipse.
> >
> > I have 3 independent projects (say A, B and C) with no common root.
> > Project A is the common project (jar) which project B and C will
> > include.
> >
> > In pom.xml in project B and project C, there is a dependency defined
> > for A. However, in eclipse, I'd like to have project B and project C
> > to include the project A as reference project instead of the jar.
> >
> > Is this possible without using the project hierarchy approach?
> >
> > HL
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven and Eclipse Project

Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.

I tried setting the following properties in pom.xml or command line:

workspace
eclipse.workspace
maven.eclipse.workspace

The command does not report any error. However, the eclipse buildpath of
project B or project C still do not reference project A.

Any idea? 

-----Original Message-----
From: Arnaud HERITIER [mailto:aheritier@gmail.com] 
Sent: August 21, 2008 1:55 PM
To: Maven Users List
Subject: Re: Maven and Eclipse Project

using the workspace property the eclipse plugin can find references to
others projects and link them.
Otherwise without having an inheritence but a reactor pom with 3 modules
will also link them together.

On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward
<Ha...@lac-bac.gc.ca>wrote:

> Hi there,
>
> I have an issue with maven classpath generation ("mvn 
> eclipse:eclipse") for eclipse.
>
> I have 3 independent projects (say A, B and C) with no common root.
> Project A is the common project (jar) which project B and C will 
> include.
>
> In pom.xml in project B and project C, there is a dependency defined 
> for A. However, in eclipse, I'd like to have project B and project C 
> to include the project A as reference project instead of the jar.
>
> Is this possible without using the project hierarchy approach?
>
> HL
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven and Eclipse Project

Posted by Arnaud HERITIER <ah...@gmail.com>.

using the workspace property the eclipse plugin can find references to
others projects and link them.
Otherwise without having an inheritence but a reactor pom with 3 modules
will also link them together.

On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward <Ha...@lac-bac.gc.ca>wrote:

> Hi there,
>
> I have an issue with maven classpath generation ("mvn eclipse:eclipse")
> for eclipse.
>
> I have 3 independent projects (say A, B and C) with no common root.
> Project A is the common project (jar) which project B and C will
> include.
>
> In pom.xml in project B and project C, there is a dependency defined for
> A. However, in eclipse, I'd like to have project B and project C to
> include the project A as reference project instead of the jar.
>
> Is this possible without using the project hierarchy approach?
>
> HL
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

Maven and Eclipse Project

Posted by Lam Hayward <Ha...@lac-bac.gc.ca>.

Hi there,

I have an issue with maven classpath generation ("mvn eclipse:eclipse")
for eclipse.

I have 3 independent projects (say A, B and C) with no common root.
Project A is the common project (jar) which project B and C will
include. 

In pom.xml in project B and project C, there is a dependency defined for
A. However, in eclipse, I'd like to have project B and project C to
include the project A as reference project instead of the jar. 

Is this possible without using the project hierarchy approach?

HL

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: AW: Release fails during SVN commit

Posted by Andreas Heinecke <an...@objectinc.de>.

Well, I used Vista SP1, JSK 1.6.0_10, Maven 2.0.9 and SlikSVN 1.5.1 (I also tried CollabNet SVN 1.5.1) and a 1.5.0 SVN server. Nothing worked until I used a 1.4.6 client.

-----Original Message-----
From: Beyer,Nathan [mailto:NBEYER@CERNER.COM] 
Sent: Thursday, August 21, 2008 8:52 PM
To: Maven 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/

-----Original Message-----
From: Andreas Heinecke [mailto:andreas@objectinc.de] 
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 the discussion and further documentation on the new features of SVN 1.5.1 to decide this. 
The important hint is that this problem doesn’t occur with a SVN 1.4 client. I did a fresh checkout with a 1.4.6 SVN client and made the release and it went through without any problems :-).

So thank you very much for that discussion and pointers to that problem. We will see if this "bug" gets fixed the next time.

-Andreas.

-----Ursprüngliche Nachricht-----
Von: Stephen Duncan Jr [mailto:stephen.duncan@gmail.com] 
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 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 <
emmanuel.venisse@gmail.com> wrote:

> 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 <dk...@apache.org> wrote:
>
> > 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 same way it does about local uncommitted changes.  But that still
> > > leaves the possibility of a commit sneaking in like you mentioned.
> > >
> > > So is there an existing bug for Svn 1.5 not being able to tag from a
> > > working copy, or does it need to be filed?
> >
> > Probably needs to be filed.
> >
> > Dan
> >
> >
> >
> > >
> > > -Stephen
> > >
> > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> > > > 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
> tag.
> > > > Something like:
> > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > > which is what release is trying to do.
> > > >
> > > > I ended up manually doing:
> > > > svn cp http://vblah.com/repo/trunk
> http://vblah.com/repo/tag/foo.1.2.3
> > > > and editing the release.properties thing to mark that the tag phase
> was
> > > > done
> > > > and then resumed it.   Kind of sucked.
> > > >
> > > > The release plugin COULD tag/branch via the trunk.   However, it
> > > > explicitly does NOT do it that way so if a commit sneaks in between
> the
> > > > commit of the poms and the tag command, that commit wouldn't be part
> of
> > > > the tag.
> > > >
> > > > Dan
> > > >
> > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > > 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:stephen.duncan@gmail.com]
> > > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > > An: Maven Users List
> > > > > Betreff: Re: Release fails during SVN commit
> > > > >
> > > > > I've had the problem as well on Ubuntu Linux, so it's a general
> > problem
> > > > > with SVN 1.5.
> > > > >
> > > > > -Stephen
> > > > >
> > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > > >
> > > > <an...@objectinc.de>wrote:
> > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each
> of
> > > >
> > > > these
> > > >
> > > > > > platforms.
> > > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > > 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, check out
> > > >
> > > >
> >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > > >
> > > > > >pro
> > > > > > blems-in-leopards-subversion/<
> > > >
> > > > http://blogs.exist.com/bporter/2008/02/25/w
> > > >
> > > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > > >
> > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I encountered a strange problem. Since a few weeks I'm not able
> > to
> > > > > > > perform a
> > > > > > > release with Maven. The release process fails during executing
> > the
> > > > > > > release:prepare goal at the same position, always. The point at
> > > > > > > which the
> > > > > > > release fails is when Maven tries to commit the release POM's
> to
> > > > > > > SVN. This
> > > > > > > commit fails with the error message that the file which is
> about
> > to
> > > >
> > > > be
> > > >
> > > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > > there. Strange, uh?
> > > > > > >
> > > > > > > I actually checked the tagbase configuration of the plugin and
> > > > > > > tried to
> > > > > > > alter it, but the effect remains.
> > > > > > > I don't know what I can try to fix this issue.
> > > > > > > The last thing altered at the configuration is a switch of the
> > SVN
> > > > > > > server.
> > > > > > > We had to switch to a newer SVN version 1.5.0. We also
> switched
> > to
> > > > > > > the new
> > > > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > > > server software and older client software.
> > > > > > >
> > > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > > >
> > > > > > > Any pointers are welcome.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Andreas.
> > > > > > >
> > > > > > > My SCM configuration:
> > > > > > > <scm>
> > > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > > > connection>
> > > > > > >
> > > > > > > <developerConnection>scm:svn:
> > http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > > >/ develope
> > > > > > > rConnection>
> > > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > > </scm>
> > > > > > >
> > > > > > > My release plugin configuration:
> > > > > > > <plugin>
> > > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > > >    <configuration>
> > > > > > >
> > > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > > >    </configuration>
> > > > > > > </plugin>
> > > > > > >
> > > > > > >
> > > > > > >
> > -------------------------------------------------------------------
> > > > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.orgFor
> > > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > > --
> > > > > >
> > > > > > LD.
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dkulp@apache.org
> > > > http://www.dankulp.com/blog
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


----------------------------------------------------------------------
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: AW: Release fails during SVN commit

Posted by "Beyer,Nathan" <NB...@CERNER.COM>.

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/

-----Original Message-----
From: Andreas Heinecke [mailto:andreas@objectinc.de] 
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 the discussion and further documentation on the new features of SVN 1.5.1 to decide this. 
The important hint is that this problem doesn’t occur with a SVN 1.4 client. I did a fresh checkout with a 1.4.6 SVN client and made the release and it went through without any problems :-).

So thank you very much for that discussion and pointers to that problem. We will see if this "bug" gets fixed the next time.

-Andreas.

-----Ursprüngliche Nachricht-----
Von: Stephen Duncan Jr [mailto:stephen.duncan@gmail.com] 
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 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 <
emmanuel.venisse@gmail.com> wrote:

> 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 <dk...@apache.org> wrote:
>
> > 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 same way it does about local uncommitted changes.  But that still
> > > leaves the possibility of a commit sneaking in like you mentioned.
> > >
> > > So is there an existing bug for Svn 1.5 not being able to tag from a
> > > working copy, or does it need to be filed?
> >
> > Probably needs to be filed.
> >
> > Dan
> >
> >
> >
> > >
> > > -Stephen
> > >
> > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> > > > 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
> tag.
> > > > Something like:
> > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > > which is what release is trying to do.
> > > >
> > > > I ended up manually doing:
> > > > svn cp http://vblah.com/repo/trunk
> http://vblah.com/repo/tag/foo.1.2.3
> > > > and editing the release.properties thing to mark that the tag phase
> was
> > > > done
> > > > and then resumed it.   Kind of sucked.
> > > >
> > > > The release plugin COULD tag/branch via the trunk.   However, it
> > > > explicitly does NOT do it that way so if a commit sneaks in between
> the
> > > > commit of the poms and the tag command, that commit wouldn't be part
> of
> > > > the tag.
> > > >
> > > > Dan
> > > >
> > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > > 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:stephen.duncan@gmail.com]
> > > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > > An: Maven Users List
> > > > > Betreff: Re: Release fails during SVN commit
> > > > >
> > > > > I've had the problem as well on Ubuntu Linux, so it's a general
> > problem
> > > > > with SVN 1.5.
> > > > >
> > > > > -Stephen
> > > > >
> > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > > >
> > > > <an...@objectinc.de>wrote:
> > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each
> of
> > > >
> > > > these
> > > >
> > > > > > platforms.
> > > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > > 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, check out
> > > >
> > > >
> >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > > >
> > > > > >pro
> > > > > > blems-in-leopards-subversion/<
> > > >
> > > > http://blogs.exist.com/bporter/2008/02/25/w
> > > >
> > > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > > >
> > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I encountered a strange problem. Since a few weeks I'm not able
> > to
> > > > > > > perform a
> > > > > > > release with Maven. The release process fails during executing
> > the
> > > > > > > release:prepare goal at the same position, always. The point at
> > > > > > > which the
> > > > > > > release fails is when Maven tries to commit the release POM's
> to
> > > > > > > SVN. This
> > > > > > > commit fails with the error message that the file which is
> about
> > to
> > > >
> > > > be
> > > >
> > > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > > there. Strange, uh?
> > > > > > >
> > > > > > > I actually checked the tagbase configuration of the plugin and
> > > > > > > tried to
> > > > > > > alter it, but the effect remains.
> > > > > > > I don't know what I can try to fix this issue.
> > > > > > > The last thing altered at the configuration is a switch of the
> > SVN
> > > > > > > server.
> > > > > > > We had to switch to a newer SVN version 1.5.0. We also
> switched
> > to
> > > > > > > the new
> > > > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > > > server software and older client software.
> > > > > > >
> > > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > > >
> > > > > > > Any pointers are welcome.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Andreas.
> > > > > > >
> > > > > > > My SCM configuration:
> > > > > > > <scm>
> > > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > > > connection>
> > > > > > >
> > > > > > > <developerConnection>scm:svn:
> > http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > > >/ develope
> > > > > > > rConnection>
> > > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > > </scm>
> > > > > > >
> > > > > > > My release plugin configuration:
> > > > > > > <plugin>
> > > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > > >    <configuration>
> > > > > > >
> > > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > > >    </configuration>
> > > > > > > </plugin>
> > > > > > >
> > > > > > >
> > > > > > >
> > -------------------------------------------------------------------
> > > > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.orgFor
> > > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > > --
> > > > > >
> > > > > > LD.
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dkulp@apache.org
> > > > http://www.dankulp.com/blog
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


----------------------------------------------------------------------
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.

AW: AW: Release fails during SVN commit

Posted by Andreas Heinecke <an...@objectinc.de>.

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 the discussion and further documentation on the new features of SVN 1.5.1 to decide this. 
The important hint is that this problem doesn’t occur with a SVN 1.4 client. I did a fresh checkout with a 1.4.6 SVN client and made the release and it went through without any problems :-).

So thank you very much for that discussion and pointers to that problem. We will see if this "bug" gets fixed the next time.

-Andreas.

-----Ursprüngliche Nachricht-----
Von: Stephen Duncan Jr [mailto:stephen.duncan@gmail.com] 
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 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 <
emmanuel.venisse@gmail.com> wrote:

> 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 <dk...@apache.org> wrote:
>
> > 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 same way it does about local uncommitted changes.  But that still
> > > leaves the possibility of a commit sneaking in like you mentioned.
> > >
> > > So is there an existing bug for Svn 1.5 not being able to tag from a
> > > working copy, or does it need to be filed?
> >
> > Probably needs to be filed.
> >
> > Dan
> >
> >
> >
> > >
> > > -Stephen
> > >
> > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> > > > 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
> tag.
> > > > Something like:
> > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > > which is what release is trying to do.
> > > >
> > > > I ended up manually doing:
> > > > svn cp http://vblah.com/repo/trunk
> http://vblah.com/repo/tag/foo.1.2.3
> > > > and editing the release.properties thing to mark that the tag phase
> was
> > > > done
> > > > and then resumed it.   Kind of sucked.
> > > >
> > > > The release plugin COULD tag/branch via the trunk.   However, it
> > > > explicitly does NOT do it that way so if a commit sneaks in between
> the
> > > > commit of the poms and the tag command, that commit wouldn't be part
> of
> > > > the tag.
> > > >
> > > > Dan
> > > >
> > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > > 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:stephen.duncan@gmail.com]
> > > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > > An: Maven Users List
> > > > > Betreff: Re: Release fails during SVN commit
> > > > >
> > > > > I've had the problem as well on Ubuntu Linux, so it's a general
> > problem
> > > > > with SVN 1.5.
> > > > >
> > > > > -Stephen
> > > > >
> > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > > >
> > > > <an...@objectinc.de>wrote:
> > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each
> of
> > > >
> > > > these
> > > >
> > > > > > platforms.
> > > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > > 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, check out
> > > >
> > > >
> >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > > >
> > > > > >pro
> > > > > > blems-in-leopards-subversion/<
> > > >
> > > > http://blogs.exist.com/bporter/2008/02/25/w
> > > >
> > > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > > >
> > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I encountered a strange problem. Since a few weeks I'm not able
> > to
> > > > > > > perform a
> > > > > > > release with Maven. The release process fails during executing
> > the
> > > > > > > release:prepare goal at the same position, always. The point at
> > > > > > > which the
> > > > > > > release fails is when Maven tries to commit the release POM's
> to
> > > > > > > SVN. This
> > > > > > > commit fails with the error message that the file which is
> about
> > to
> > > >
> > > > be
> > > >
> > > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > > there. Strange, uh?
> > > > > > >
> > > > > > > I actually checked the tagbase configuration of the plugin and
> > > > > > > tried to
> > > > > > > alter it, but the effect remains.
> > > > > > > I don't know what I can try to fix this issue.
> > > > > > > The last thing altered at the configuration is a switch of the
> > SVN
> > > > > > > server.
> > > > > > > We had to switch to a newer SVN version 1.5.0. We also
> switched
> > to
> > > > > > > the new
> > > > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > > > server software and older client software.
> > > > > > >
> > > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > > >
> > > > > > > Any pointers are welcome.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Andreas.
> > > > > > >
> > > > > > > My SCM configuration:
> > > > > > > <scm>
> > > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > > > connection>
> > > > > > >
> > > > > > > <developerConnection>scm:svn:
> > http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > > >/ develope
> > > > > > > rConnection>
> > > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > > </scm>
> > > > > > >
> > > > > > > My release plugin configuration:
> > > > > > > <plugin>
> > > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > > >    <configuration>
> > > > > > >
> > > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > > >    </configuration>
> > > > > > > </plugin>
> > > > > > >
> > > > > > >
> > > > > > >
> > -------------------------------------------------------------------
> > > > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.orgFor
> > > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > > --
> > > > > >
> > > > > > LD.
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dkulp@apache.org
> > > > http://www.dankulp.com/blog
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by Emmanuel Venisse <em...@gmail.com>.

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 <stephen.duncan@gmail.com
> wrote:

> 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 <
> emmanuel.venisse@gmail.com> wrote:
>
> > 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 <dk...@apache.org> wrote:
> >
> > > 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 same way it does about local uncommitted changes.  But that still
> > > > leaves the possibility of a commit sneaking in like you mentioned.
> > > >
> > > > So is there an existing bug for Svn 1.5 not being able to tag from a
> > > > working copy, or does it need to be filed?
> > >
> > > Probably needs to be filed.
> > >
> > > Dan
> > >
> > >
> > >
> > > >
> > > > -Stephen
> > > >
> > > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org>
> > wrote:
> > > > > 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
> > tag.
> > > > > Something like:
> > > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > > > which is what release is trying to do.
> > > > >
> > > > > I ended up manually doing:
> > > > > svn cp http://vblah.com/repo/trunk
> > http://vblah.com/repo/tag/foo.1.2.3
> > > > > and editing the release.properties thing to mark that the tag phase
> > was
> > > > > done
> > > > > and then resumed it.   Kind of sucked.
> > > > >
> > > > > The release plugin COULD tag/branch via the trunk.   However, it
> > > > > explicitly does NOT do it that way so if a commit sneaks in between
> > the
> > > > > commit of the poms and the tag command, that commit wouldn't be
> part
> > of
> > > > > the tag.
> > > > >
> > > > > Dan
> > > > >
> > > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > > > 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:stephen.duncan@gmail.com]
> > > > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > > > An: Maven Users List
> > > > > > Betreff: Re: Release fails during SVN commit
> > > > > >
> > > > > > I've had the problem as well on Ubuntu Linux, so it's a general
> > > problem
> > > > > > with SVN 1.5.
> > > > > >
> > > > > > -Stephen
> > > > > >
> > > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > > > >
> > > > > <an...@objectinc.de>wrote:
> > > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each
> > of
> > > > >
> > > > > these
> > > > >
> > > > > > > platforms.
> > > > > > >
> > > > > > > -----Ursprüngliche Nachricht-----
> > > > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > > > 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, check out
> > > > >
> > > > >
> > >
> >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > > > >
> > > > > > >pro
> > > > > > > blems-in-leopards-subversion/<
> > > > >
> > > > > http://blogs.exist.com/bporter/2008/02/25/w
> > > > >
> > > > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > > > >
> > > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > > > Hi there,
> > > > > > > >
> > > > > > > > I encountered a strange problem. Since a few weeks I'm not
> able
> > > to
> > > > > > > > perform a
> > > > > > > > release with Maven. The release process fails during
> executing
> > > the
> > > > > > > > release:prepare goal at the same position, always. The point
> at
> > > > > > > > which the
> > > > > > > > release fails is when Maven tries to commit the release POM's
> > to
> > > > > > > > SVN. This
> > > > > > > > commit fails with the error message that the file which is
> > about
> > > to
> > > > >
> > > > > be
> > > > >
> > > > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > > > there. Strange, uh?
> > > > > > > >
> > > > > > > > I actually checked the tagbase configuration of the plugin
> and
> > > > > > > > tried to
> > > > > > > > alter it, but the effect remains.
> > > > > > > > I don't know what I can try to fix this issue.
> > > > > > > > The last thing altered at the configuration is a switch of
> the
> > > SVN
> > > > > > > > server.
> > > > > > > > We had to switch to a newer SVN version 1.5.0. We also
> > switched
> > > to
> > > > > > > > the new
> > > > > > > > 1.5.0 SVN client as we know that there are problems with
> newer
> > > > > > > > server software and older client software.
> > > > > > > >
> > > > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > > > >
> > > > > > > > Any pointers are welcome.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Andreas.
> > > > > > > >
> > > > > > > > My SCM configuration:
> > > > > > > > <scm>
> > > > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project
> </
> > > > > > > > connection>
> > > > > > > >
> > > > > > > > <developerConnection>scm:svn:
> > > http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > > > >/ develope
> > > > > > > > rConnection>
> > > > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > > > </scm>
> > > > > > > >
> > > > > > > > My release plugin configuration:
> > > > > > > > <plugin>
> > > > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > > > >    <configuration>
> > > > > > > >
> > > > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags
> </tagBase>
> > > > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > > > >    </configuration>
> > > > > > > > </plugin>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > -------------------------------------------------------------------
> > > > > > > >-- To unsubscribe, e-mail:
> users-unsubscribe@maven.apache.orgFor
> > > > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > LD.
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > > --
> > > > > Daniel Kulp
> > > > > dkulp@apache.org
> > > > > http://www.dankulp.com/blog
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://www.dankulp.com/blog
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
>
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

Re: AW: Release fails during SVN commit

Posted by Stephen Duncan Jr <st...@gmail.com>.

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 <
emmanuel.venisse@gmail.com> wrote:

> 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 <dk...@apache.org> wrote:
>
> > 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 same way it does about local uncommitted changes.  But that still
> > > leaves the possibility of a commit sneaking in like you mentioned.
> > >
> > > So is there an existing bug for Svn 1.5 not being able to tag from a
> > > working copy, or does it need to be filed?
> >
> > Probably needs to be filed.
> >
> > Dan
> >
> >
> >
> > >
> > > -Stephen
> > >
> > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> > > > 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
> tag.
> > > > Something like:
> > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > > which is what release is trying to do.
> > > >
> > > > I ended up manually doing:
> > > > svn cp http://vblah.com/repo/trunk
> http://vblah.com/repo/tag/foo.1.2.3
> > > > and editing the release.properties thing to mark that the tag phase
> was
> > > > done
> > > > and then resumed it.   Kind of sucked.
> > > >
> > > > The release plugin COULD tag/branch via the trunk.   However, it
> > > > explicitly does NOT do it that way so if a commit sneaks in between
> the
> > > > commit of the poms and the tag command, that commit wouldn't be part
> of
> > > > the tag.
> > > >
> > > > Dan
> > > >
> > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > > 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:stephen.duncan@gmail.com]
> > > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > > An: Maven Users List
> > > > > Betreff: Re: Release fails during SVN commit
> > > > >
> > > > > I've had the problem as well on Ubuntu Linux, so it's a general
> > problem
> > > > > with SVN 1.5.
> > > > >
> > > > > -Stephen
> > > > >
> > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > > >
> > > > <an...@objectinc.de>wrote:
> > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each
> of
> > > >
> > > > these
> > > >
> > > > > > platforms.
> > > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > > 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, check out
> > > >
> > > >
> >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > > >
> > > > > >pro
> > > > > > blems-in-leopards-subversion/<
> > > >
> > > > http://blogs.exist.com/bporter/2008/02/25/w
> > > >
> > > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > > >
> > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I encountered a strange problem. Since a few weeks I'm not able
> > to
> > > > > > > perform a
> > > > > > > release with Maven. The release process fails during executing
> > the
> > > > > > > release:prepare goal at the same position, always. The point at
> > > > > > > which the
> > > > > > > release fails is when Maven tries to commit the release POM's
> to
> > > > > > > SVN. This
> > > > > > > commit fails with the error message that the file which is
> about
> > to
> > > >
> > > > be
> > > >
> > > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > > there. Strange, uh?
> > > > > > >
> > > > > > > I actually checked the tagbase configuration of the plugin and
> > > > > > > tried to
> > > > > > > alter it, but the effect remains.
> > > > > > > I don't know what I can try to fix this issue.
> > > > > > > The last thing altered at the configuration is a switch of the
> > SVN
> > > > > > > server.
> > > > > > > We had to switch to a newer SVN version 1.5.0. We also
> switched
> > to
> > > > > > > the new
> > > > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > > > server software and older client software.
> > > > > > >
> > > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > > >
> > > > > > > Any pointers are welcome.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Andreas.
> > > > > > >
> > > > > > > My SCM configuration:
> > > > > > > <scm>
> > > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > > > connection>
> > > > > > >
> > > > > > > <developerConnection>scm:svn:
> > http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > > >/ develope
> > > > > > > rConnection>
> > > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > > </scm>
> > > > > > >
> > > > > > > My release plugin configuration:
> > > > > > > <plugin>
> > > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > > >    <configuration>
> > > > > > >
> > > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > > >    </configuration>
> > > > > > > </plugin>
> > > > > > >
> > > > > > >
> > > > > > >
> > -------------------------------------------------------------------
> > > > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.orgFor
> > > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > > --
> > > > > >
> > > > > > LD.
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dkulp@apache.org
> > > > http://www.dankulp.com/blog
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: AW: Release fails during SVN commit

Posted by Emmanuel Venisse <em...@gmail.com>.

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 <dk...@apache.org> wrote:

> 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 same way it does about local uncommitted changes.  But that still
> > leaves the possibility of a commit sneaking in like you mentioned.
> >
> > So is there an existing bug for Svn 1.5 not being able to tag from a
> > working copy, or does it need to be filed?
>
> Probably needs to be filed.
>
> Dan
>
>
>
> >
> > -Stephen
> >
> > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org> wrote:
> > > 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 tag.
> > > Something like:
> > > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > > which is what release is trying to do.
> > >
> > > I ended up manually doing:
> > > svn cp http://vblah.com/repo/trunk http://vblah.com/repo/tag/foo.1.2.3
> > > and editing the release.properties thing to mark that the tag phase was
> > > done
> > > and then resumed it.   Kind of sucked.
> > >
> > > The release plugin COULD tag/branch via the trunk.   However, it
> > > explicitly does NOT do it that way so if a commit sneaks in between the
> > > commit of the poms and the tag command, that commit wouldn't be part of
> > > the tag.
> > >
> > > Dan
> > >
> > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > > 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:stephen.duncan@gmail.com]
> > > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > > An: Maven Users List
> > > > Betreff: Re: Release fails during SVN commit
> > > >
> > > > I've had the problem as well on Ubuntu Linux, so it's a general
> problem
> > > > with SVN 1.5.
> > > >
> > > > -Stephen
> > > >
> > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> > >
> > > <an...@objectinc.de>wrote:
> > > > > No, we use MS Windows Vista, and XP. The problem occurs on each of
> > >
> > > these
> > >
> > > > > platforms.
> > > > >
> > > > > -----Ursprüngliche Nachricht-----
> > > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > > 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, check out
> > >
> > >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > >
> > > > >pro
> > > > > blems-in-leopards-subversion/<
> > >
> > > http://blogs.exist.com/bporter/2008/02/25/w
> > >
> > > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > > >
> > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > > Hi there,
> > > > > >
> > > > > > I encountered a strange problem. Since a few weeks I'm not able
> to
> > > > > > perform a
> > > > > > release with Maven. The release process fails during executing
> the
> > > > > > release:prepare goal at the same position, always. The point at
> > > > > > which the
> > > > > > release fails is when Maven tries to commit the release POM's to
> > > > > > SVN. This
> > > > > > commit fails with the error message that the file which is about
> to
> > >
> > > be
> > >
> > > > > > committed already exists at the position in SVN. But it isn't
> > > > > > there. Strange, uh?
> > > > > >
> > > > > > I actually checked the tagbase configuration of the plugin and
> > > > > > tried to
> > > > > > alter it, but the effect remains.
> > > > > > I don't know what I can try to fix this issue.
> > > > > > The last thing altered at the configuration is a switch of the
> SVN
> > > > > > server.
> > > > > > We had to switch to a newer SVN version 1.5.0. We also switched
> to
> > > > > > the new
> > > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > > server software and older client software.
> > > > > >
> > > > > > Please find parts of my pom.xml configuration attached below.
> > > > > >
> > > > > > Any pointers are welcome.
> > > > > >
> > > > > > Regards,
> > > > > > Andreas.
> > > > > >
> > > > > > My SCM configuration:
> > > > > > <scm>
> > > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > > connection>
> > > > > >
> > > > > > <developerConnection>scm:svn:
> http://xxx.xxx.xxx.xxx/svndir/project<
> > > > > >/ develope
> > > > > > rConnection>
> > > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > > </scm>
> > > > > >
> > > > > > My release plugin configuration:
> > > > > > <plugin>
> > > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > > >    <configuration>
> > > > > >
> > > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > > <preparationGoals>clean install</preparationGoals>
> > > > > >    </configuration>
> > > > > > </plugin>
> > > > > >
> > > > > >
> > > > > >
> -------------------------------------------------------------------
> > > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For
> > > > > > additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > > --
> > > > >
> > > > > LD.
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://www.dankulp.com/blog
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: AW: Release fails during SVN commit

Posted by Daniel Kulp <dk...@apache.org>.

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 same way it does about local uncommitted changes.  But that still
> leaves the possibility of a commit sneaking in like you mentioned.
>
> So is there an existing bug for Svn 1.5 not being able to tag from a
> working copy, or does it need to be filed?

Probably needs to be filed.  

Dan



>
> -Stephen
>
> On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org> wrote:
> > 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 tag.
> > Something like:
> > svn cp . http://vblah.com/repo/tag/foo.1.2.3
> > which is what release is trying to do.
> >
> > I ended up manually doing:
> > svn cp http://vblah.com/repo/trunk http://vblah.com/repo/tag/foo.1.2.3
> > and editing the release.properties thing to mark that the tag phase was
> > done
> > and then resumed it.   Kind of sucked.
> >
> > The release plugin COULD tag/branch via the trunk.   However, it
> > explicitly does NOT do it that way so if a commit sneaks in between the
> > commit of the poms and the tag command, that commit wouldn't be part of
> > the tag.
> >
> > Dan
> >
> > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > > 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:stephen.duncan@gmail.com]
> > > Gesendet: Donnerstag, 21. August 2008 14:48
> > > An: Maven Users List
> > > Betreff: Re: Release fails during SVN commit
> > >
> > > I've had the problem as well on Ubuntu Linux, so it's a general problem
> > > with SVN 1.5.
> > >
> > > -Stephen
> > >
> > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> >
> > <an...@objectinc.de>wrote:
> > > > No, we use MS Windows Vista, and XP. The problem occurs on each of
> >
> > these
> >
> > > > platforms.
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > > 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, check out
> >
> > http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> >
> > > >pro
> > > > blems-in-leopards-subversion/<
> >
> > http://blogs.exist.com/bporter/2008/02/25/w
> >
> > > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > > >
> > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > > Hi there,
> > > > >
> > > > > I encountered a strange problem. Since a few weeks I'm not able to
> > > > > perform a
> > > > > release with Maven. The release process fails during executing the
> > > > > release:prepare goal at the same position, always. The point at
> > > > > which the
> > > > > release fails is when Maven tries to commit the release POM's to
> > > > > SVN. This
> > > > > commit fails with the error message that the file which is about to
> >
> > be
> >
> > > > > committed already exists at the position in SVN. But it isn't
> > > > > there. Strange, uh?
> > > > >
> > > > > I actually checked the tagbase configuration of the plugin and
> > > > > tried to
> > > > > alter it, but the effect remains.
> > > > > I don't know what I can try to fix this issue.
> > > > > The last thing altered at the configuration is a switch of the SVN
> > > > > server.
> > > > > We had to switch to a newer SVN version 1.5.0. We also switched to
> > > > > the new
> > > > > 1.5.0 SVN client as we know that there are problems with newer
> > > > > server software and older client software.
> > > > >
> > > > > Please find parts of my pom.xml configuration attached below.
> > > > >
> > > > > Any pointers are welcome.
> > > > >
> > > > > Regards,
> > > > > Andreas.
> > > > >
> > > > > My SCM configuration:
> > > > > <scm>
> > > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > > connection>
> > > > >
> > > > > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project<
> > > > >/ develope
> > > > > rConnection>
> > > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > > </scm>
> > > > >
> > > > > My release plugin configuration:
> > > > > <plugin>
> > > > >    <groupId>org.apache.maven.plugins</groupId>
> > > > >    <artifactId>maven-release-plugin</artifactId>
> > > > >    <configuration>
> > > > >       
> > > > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > > > <autoVersionSubmodules>true</autoVersionSubmodules>
> > > > > <preparationGoals>clean install</preparationGoals>
> > > > >    </configuration>
> > > > > </plugin>
> > > > >
> > > > >
> > > > > -------------------------------------------------------------------
> > > > >-- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For
> > > > > additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > --
> > > >
> > > > LD.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org



-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by Stephen Duncan Jr <st...@gmail.com>.

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 the
possibility of a commit sneaking in like you mentioned.

So is there an existing bug for Svn 1.5 not being able to tag from a working
copy, or does it need to be filed?

-Stephen

On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <dk...@apache.org> wrote:

>
> 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 tag.
> Something like:
> svn cp . http://vblah.com/repo/tag/foo.1.2.3
> which is what release is trying to do.
>
> I ended up manually doing:
> svn cp http://vblah.com/repo/trunk http://vblah.com/repo/tag/foo.1.2.3
> and editing the release.properties thing to mark that the tag phase was
> done
> and then resumed it.   Kind of sucked.
>
> The release plugin COULD tag/branch via the trunk.   However, it explicitly
> does NOT do it that way so if a commit sneaks in between the commit of the
> poms and the tag command, that commit wouldn't be part of the tag.
>
> Dan
>
>
>
> On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> > 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:stephen.duncan@gmail.com]
> > Gesendet: Donnerstag, 21. August 2008 14:48
> > An: Maven Users List
> > Betreff: Re: Release fails during SVN commit
> >
> > I've had the problem as well on Ubuntu Linux, so it's a general problem
> > with SVN 1.5.
> >
> > -Stephen
> >
> > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke
> <an...@objectinc.de>wrote:
> > > No, we use MS Windows Vista, and XP. The problem occurs on each of
> these
> > > platforms.
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Luke Daley [mailto:ld@ldaley.com]
> > > 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, check out
> > >
> > >
> > >
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> > >pro
> > > blems-in-leopards-subversion/<
> http://blogs.exist.com/bporter/2008/02/25/w
> > >orking-around-non-interactive-problems-in-leopards-subversion/>
> > >
> > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > > Hi there,
> > > >
> > > > I encountered a strange problem. Since a few weeks I'm not able to
> > > > perform a
> > > > release with Maven. The release process fails during executing the
> > > > release:prepare goal at the same position, always. The point at
> > > > which the
> > > > release fails is when Maven tries to commit the release POM's to
> > > > SVN. This
> > > > commit fails with the error message that the file which is about to
> be
> > > > committed already exists at the position in SVN. But it isn't there.
> > > > Strange, uh?
> > > >
> > > > I actually checked the tagbase configuration of the plugin and tried
> > > > to
> > > > alter it, but the effect remains.
> > > > I don't know what I can try to fix this issue.
> > > > The last thing altered at the configuration is a switch of the SVN
> > > > server.
> > > > We had to switch to a newer SVN version 1.5.0. We also switched to
> > > > the new
> > > > 1.5.0 SVN client as we know that there are problems with newer server
> > > > software and older client software.
> > > >
> > > > Please find parts of my pom.xml configuration attached below.
> > > >
> > > > Any pointers are welcome.
> > > >
> > > > Regards,
> > > > Andreas.
> > > >
> > > > My SCM configuration:
> > > > <scm>
> > > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > connection>
> > > >
> > > > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > > develope
> > > > rConnection>
> > > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > > </scm>
> > > >
> > > > My release plugin configuration:
> > > > <plugin>
> > > >    <groupId>org.apache.maven.plugins</groupId>
> > > >    <artifactId>maven-release-plugin</artifactId>
> > > >    <configuration>
> > > >        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > > >        <autoVersionSubmodules>true</autoVersionSubmodules>
> > > >        <preparationGoals>clean install</preparationGoals>
> > > >    </configuration>
> > > > </plugin>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > --
> > >
> > > LD.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: AW: Release fails during SVN commit

Posted by Daniel Kulp <dk...@apache.org>.

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 tag.  
Something like:
svn cp . http://vblah.com/repo/tag/foo.1.2.3
which is what release is trying to do.  

I ended up manually doing:
svn cp http://vblah.com/repo/trunk http://vblah.com/repo/tag/foo.1.2.3
and editing the release.properties thing to mark that the tag phase was done 
and then resumed it.   Kind of sucked.

The release plugin COULD tag/branch via the trunk.   However, it explicitly 
does NOT do it that way so if a commit sneaks in between the commit of the 
poms and the tag command, that commit wouldn't be part of the tag.

Dan



On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote:
> 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:stephen.duncan@gmail.com]
> Gesendet: Donnerstag, 21. August 2008 14:48
> An: Maven Users List
> Betreff: Re: Release fails during SVN commit
>
> I've had the problem as well on Ubuntu Linux, so it's a general problem
> with SVN 1.5.
>
> -Stephen
>
> On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke 
<an...@objectinc.de>wrote:
> > No, we use MS Windows Vista, and XP. The problem occurs on each of these
> > platforms.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Luke Daley [mailto:ld@ldaley.com]
> > 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, check out
> >
> >
> > http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-
> >pro
> > blems-in-leopards-subversion/<http://blogs.exist.com/bporter/2008/02/25/w
> >orking-around-non-interactive-problems-in-leopards-subversion/>
> >
> > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
> > > Hi there,
> > >
> > > I encountered a strange problem. Since a few weeks I'm not able to
> > > perform a
> > > release with Maven. The release process fails during executing the
> > > release:prepare goal at the same position, always. The point at
> > > which the
> > > release fails is when Maven tries to commit the release POM's to
> > > SVN. This
> > > commit fails with the error message that the file which is about to be
> > > committed already exists at the position in SVN. But it isn't there.
> > > Strange, uh?
> > >
> > > I actually checked the tagbase configuration of the plugin and tried
> > > to
> > > alter it, but the effect remains.
> > > I don't know what I can try to fix this issue.
> > > The last thing altered at the configuration is a switch of the SVN
> > > server.
> > > We had to switch to a newer SVN version 1.5.0. We also switched to
> > > the new
> > > 1.5.0 SVN client as we know that there are problems with newer server
> > > software and older client software.
> > >
> > > Please find parts of my pom.xml configuration attached below.
> > >
> > > Any pointers are welcome.
> > >
> > > Regards,
> > > Andreas.
> > >
> > > My SCM configuration:
> > > <scm>
> > >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > connection>
> > >
> > > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > > develope
> > > rConnection>
> > >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > > </scm>
> > >
> > > My release plugin configuration:
> > > <plugin>
> > >    <groupId>org.apache.maven.plugins</groupId>
> > >    <artifactId>maven-release-plugin</artifactId>
> > >    <configuration>
> > >        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> > >        <autoVersionSubmodules>true</autoVersionSubmodules>
> > >        <preparationGoals>clean install</preparationGoals>
> > >    </configuration>
> > > </plugin>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> > --
> >
> > LD.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org



-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

AW: Release fails during SVN commit

Posted by Andreas Heinecke <an...@objectinc.de>.

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:stephen.duncan@gmail.com] 
Gesendet: Donnerstag, 21. August 2008 14:48
An: Maven Users List
Betreff: Re: Release fails during SVN commit

I've had the problem as well on Ubuntu Linux, so it's a general problem with
SVN 1.5.

-Stephen

On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke <an...@objectinc.de>wrote:

> No, we use MS Windows Vista, and XP. The problem occurs on each of these
> platforms.
>
> -----Ursprüngliche Nachricht-----
> Von: Luke Daley [mailto:ld@ldaley.com]
> 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, check out
>
>
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-pro
> blems-in-leopards-subversion/<http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/>
>
> On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
>
> > Hi there,
> >
> > I encountered a strange problem. Since a few weeks I'm not able to
> > perform a
> > release with Maven. The release process fails during executing the
> > release:prepare goal at the same position, always. The point at
> > which the
> > release fails is when Maven tries to commit the release POM's to
> > SVN. This
> > commit fails with the error message that the file which is about to be
> > committed already exists at the position in SVN. But it isn't there.
> > Strange, uh?
> >
> > I actually checked the tagbase configuration of the plugin and tried
> > to
> > alter it, but the effect remains.
> > I don't know what I can try to fix this issue.
> > The last thing altered at the configuration is a switch of the SVN
> > server.
> > We had to switch to a newer SVN version 1.5.0. We also switched to
> > the new
> > 1.5.0 SVN client as we know that there are problems with newer server
> > software and older client software.
> >
> > Please find parts of my pom.xml configuration attached below.
> >
> > Any pointers are welcome.
> >
> > Regards,
> > Andreas.
> >
> > My SCM configuration:
> > <scm>
> >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > connection>
> >
> > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > develope
> > rConnection>
> >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > </scm>
> >
> > My release plugin configuration:
> > <plugin>
> >    <groupId>org.apache.maven.plugins</groupId>
> >    <artifactId>maven-release-plugin</artifactId>
> >    <configuration>
> >        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> >        <autoVersionSubmodules>true</autoVersionSubmodules>
> >        <preparationGoals>clean install</preparationGoals>
> >    </configuration>
> > </plugin>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
>
> LD.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Release fails during SVN commit

Posted by Stephen Duncan Jr <st...@gmail.com>.

I've had the problem as well on Ubuntu Linux, so it's a general problem with
SVN 1.5.

-Stephen

On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke <an...@objectinc.de>wrote:

> No, we use MS Windows Vista, and XP. The problem occurs on each of these
> platforms.
>
> -----Ursprüngliche Nachricht-----
> Von: Luke Daley [mailto:ld@ldaley.com]
> 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, check out
>
>
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-pro
> blems-in-leopards-subversion/<http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/>
>
> On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:
>
> > Hi there,
> >
> > I encountered a strange problem. Since a few weeks I'm not able to
> > perform a
> > release with Maven. The release process fails during executing the
> > release:prepare goal at the same position, always. The point at
> > which the
> > release fails is when Maven tries to commit the release POM's to
> > SVN. This
> > commit fails with the error message that the file which is about to be
> > committed already exists at the position in SVN. But it isn't there.
> > Strange, uh?
> >
> > I actually checked the tagbase configuration of the plugin and tried
> > to
> > alter it, but the effect remains.
> > I don't know what I can try to fix this issue.
> > The last thing altered at the configuration is a switch of the SVN
> > server.
> > We had to switch to a newer SVN version 1.5.0. We also switched to
> > the new
> > 1.5.0 SVN client as we know that there are problems with newer server
> > software and older client software.
> >
> > Please find parts of my pom.xml configuration attached below.
> >
> > Any pointers are welcome.
> >
> > Regards,
> > Andreas.
> >
> > My SCM configuration:
> > <scm>
> >    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > connection>
> >
> > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</
> > develope
> > rConnection>
> >    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > </scm>
> >
> > My release plugin configuration:
> > <plugin>
> >    <groupId>org.apache.maven.plugins</groupId>
> >    <artifactId>maven-release-plugin</artifactId>
> >    <configuration>
> >        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> >        <autoVersionSubmodules>true</autoVersionSubmodules>
> >        <preparationGoals>clean install</preparationGoals>
> >    </configuration>
> > </plugin>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
>
> LD.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

AW: Release fails during SVN commit

Posted by Andreas Heinecke <an...@objectinc.de>.

No, we use MS Windows Vista, and XP. The problem occurs on each of these
platforms.

-----Ursprüngliche Nachricht-----
Von: Luke Daley [mailto:ld@ldaley.com] 
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, check out

http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-pro
blems-in-leopards-subversion/

On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:

> Hi there,
>
> I encountered a strange problem. Since a few weeks I'm not able to  
> perform a
> release with Maven. The release process fails during executing the
> release:prepare goal at the same position, always. The point at  
> which the
> release fails is when Maven tries to commit the release POM's to  
> SVN. This
> commit fails with the error message that the file which is about to be
> committed already exists at the position in SVN. But it isn't there.
> Strange, uh?
>
> I actually checked the tagbase configuration of the plugin and tried  
> to
> alter it, but the effect remains.
> I don't know what I can try to fix this issue.
> The last thing altered at the configuration is a switch of the SVN  
> server.
> We had to switch to a newer SVN version 1.5.0. We also switched to  
> the new
> 1.5.0 SVN client as we know that there are problems with newer server
> software and older client software.
>
> Please find parts of my pom.xml configuration attached below.
>
> Any pointers are welcome.
>
> Regards,
> Andreas.
>
> My SCM configuration:
> <scm>
>    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</ 
> connection>
>
> <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</ 
> develope
> rConnection>
>    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> </scm>
>
> My release plugin configuration:
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-release-plugin</artifactId>
>    <configuration>
>        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>        <autoVersionSubmodules>true</autoVersionSubmodules>
>        <preparationGoals>clean install</preparationGoals>
>    </configuration>
> </plugin>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

--

LD.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Release fails during SVN commit

Posted by Luke Daley <ld...@ldaley.com>.

If your on Mac OS 10.5, check out

http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/

On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote:

> Hi there,
>
> I encountered a strange problem. Since a few weeks I'm not able to  
> perform a
> release with Maven. The release process fails during executing the
> release:prepare goal at the same position, always. The point at  
> which the
> release fails is when Maven tries to commit the release POM's to  
> SVN. This
> commit fails with the error message that the file which is about to be
> committed already exists at the position in SVN. But it isn't there.
> Strange, uh?
>
> I actually checked the tagbase configuration of the plugin and tried  
> to
> alter it, but the effect remains.
> I don't know what I can try to fix this issue.
> The last thing altered at the configuration is a switch of the SVN  
> server.
> We had to switch to a newer SVN version 1.5.0. We also switched to  
> the new
> 1.5.0 SVN client as we know that there are problems with newer server
> software and older client software.
>
> Please find parts of my pom.xml configuration attached below.
>
> Any pointers are welcome.
>
> Regards,
> Andreas.
>
> My SCM configuration:
> <scm>
>    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</ 
> connection>
>
> <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</ 
> develope
> rConnection>
>    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> </scm>
>
> My release plugin configuration:
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-release-plugin</artifactId>
>    <configuration>
>        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>        <autoVersionSubmodules>true</autoVersionSubmodules>
>        <preparationGoals>clean install</preparationGoals>
>    </configuration>
> </plugin>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

--

LD.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by mzgubin <mz...@gmail.com>.

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 correct location in
your svn.
I kept getting this error until i've resolved that first. 
Also, this assumes that you have a typical SVN structure: with trunk,
branches and tags in the same folder.  If you don't have a typical layout,
then maven-release-plugin's configuration will have to be modified and a
tagBase specified.

Example:

<scm>
   
<connection>scm:svn:svn+ssh://username@svn.repository.com/local/project/svn/devrepo/project/trunk</connection>
   
<developerConnection>scm:svn:svn+ssh://username@svn.repository.com/local/project/svn/devrepo/project/trunk</developerConnection>
    <url>http://svn.repository.com</url>
  </scm>
  
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-release-plugin</artifactId>
      </plugin>
    </plugins>
  </build>

BTW, currently i'm running the latest subversion client (1.5.2)



doballve wrote:
> 
> 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
>  * run svn copy manually, do not use --non-interactive, and you'll have to
> provide a message
>  * edit release.properties, advance the completed phase
>     - completedPhase=scm-commit-release
>    + completedPhase=scm-tag
> * run mvn release:prepare to continue the release
> * proceed normally with release:perform and so on..
> 
> If anybody has the proper solution for this issue, I'd be glad to know it.
> 
> Thanks,
> Diego
> 

-- 
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19807745.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by doballve <di...@digital-artefacts.fi>.

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
 * run svn copy manually, do not use --non-interactive, and you'll have to
provide a message
 * edit release.properties, advance the completed phase
    - completedPhase=scm-commit-release
   + completedPhase=scm-tag
* run mvn release:prepare to continue the release
* proceed normally with release:perform and so on..

If anybody has the proper solution for this issue, I'd be glad to know it.

Thanks,
Diego
-- 
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19586036.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by Arnaud HERITIER <ah...@gmail.com>.

Same error for me with SVN 1.5.1 on windows.
It's not a MAC only issue
Coming back to 1.4.6 solves the issue

Arnaud

On Tue, Aug 26, 2008 at 5:17 PM, Glase, Stefan <
Stefan.Glase@opitz-consulting.de> wrote:

> Hello David,
>
> I just updated to Subversion version 1.5.1 (r32289) and now i am 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:nabble@diroussel.xsmail.com]
> Gesendet: Dienstag, 26. 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 the command that fails:
>
>  svn --non-interactive copy --file
> C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1777868452.commit .
> http://svnserver/svn/REPO1/Projects/InstallTools/tags/installer-0.5
>
> also fails if I run it manually, but if I run 'svn up' then rerun it, it
> works.
>
> It's as if the previous commit has not updated the working copy in someway.
>
> I tried to reproduce the problem in pure svn commands, creating a new repo,
> adding files, tagging, then going back to a previous revision, then tagging
> again.  But I was unable to reproduce it.
>
> Perhaps there is a way to get the SCM plugin to log every command it runs,
> see which step is not updating the working copy.
>
> Thanks
>
> David
>
>
>
> Glase, Stefan wrote:
> >
> > 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:
> >
> > <scm>
> >     <connection>scm:svn:http://xxx/svndir/project/trunk</connection>
> >     <developerConnection>scm:svn:http://xxx
> > /svndir/project/trunk</develope
> > rConnection>
> >     <url>http://xxx /svndir/project/</url>
> > </scm>
> >
> > ...
> >
> > <plugin>
> >     <groupId>org.apache.maven.plugins</groupId>
> >     <artifactId>maven-release-plugin</artifactId>
> >     <configuration>
> >         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> >         <autoVersionSubmodules>true</autoVersionSubmodules>
> >         <preparationGoals>clean install</preparationGoals>
> >     </configuration>
> > </plugin>
> >
> > My idea behind this is, that it might be a problem to point to a
> > tag-directory within the scm connection. I my understanding those folders
> > should be on the same level.
> >
> > Hope to help
> > Stefan
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Andreas Heinecke [mailto:andreas@objectinc.de]
> > Gesendet: Donnerstag, 21. August 2008 10:04
> > An: users@maven.apache.org
> > Betreff: Release fails during SVN commit
> >
> > Hi there,
> >
> > I encountered a strange problem. Since a few weeks I'm not able to
> perform
> > a
> > release with Maven. The release process fails during executing the
> > release:prepare goal at the same position, always. The point at which the
> > release fails is when Maven tries to commit the release POM's to SVN.
> This
> > commit fails with the error message that the file which is about to be
> > committed already exists at the position in SVN. But it isn't there.
> > Strange, uh?
> >
> > I actually checked the tagbase configuration of the plugin and tried to
> > alter it, but the effect remains.
> > I don't know what I can try to fix this issue.
> > The last thing altered at the configuration is a switch of the SVN
> server.
> > We had to switch to a newer SVN version 1.5.0. We also switched to the
> new
> > 1.5.0 SVN client as we know that there are problems with newer server
> > software and older client software.
> >
> > Please find parts of my pom.xml configuration attached below.
> >
> > Any pointers are welcome.
> >
> > Regards,
> > Andreas.
> >
> > My SCM configuration:
> > <scm>
> >     <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project
> </connection>
> >
> > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project
> </develope
> > rConnection>
> >     <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> > </scm>
> >
> > My release plugin configuration:
> > <plugin>
> >     <groupId>org.apache.maven.plugins</groupId>
> >     <artifactId>maven-release-plugin</artifactId>
> >     <configuration>
> >         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
> >         <autoVersionSubmodules>true</autoVersionSubmodules>
> >         <preparationGoals>clean install</preparationGoals>
> >     </configuration>
> > </plugin>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19163336.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

AW: AW: Release fails during SVN commit

Posted by "Glase, Stefan" <St...@opitz-consulting.de>.

Hello David,

I just updated to Subversion version 1.5.1 (r32289) and now i am 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:nabble@diroussel.xsmail.com]
Gesendet: Dienstag, 26. 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 the command that fails:

  svn --non-interactive copy --file
C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1777868452.commit .
http://svnserver/svn/REPO1/Projects/InstallTools/tags/installer-0.5

also fails if I run it manually, but if I run 'svn up' then rerun it, it
works.

It's as if the previous commit has not updated the working copy in someway.

I tried to reproduce the problem in pure svn commands, creating a new repo,
adding files, tagging, then going back to a previous revision, then tagging
again.  But I was unable to reproduce it.

Perhaps there is a way to get the SCM plugin to log every command it runs,
see which step is not updating the working copy.

Thanks

David



Glase, Stefan wrote:
>
> 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:
>
> <scm>
>     <connection>scm:svn:http://xxx/svndir/project/trunk</connection>
>     <developerConnection>scm:svn:http://xxx
> /svndir/project/trunk</develope
> rConnection>
>     <url>http://xxx /svndir/project/</url>
> </scm>
>
> ...
>
> <plugin>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-release-plugin</artifactId>
>     <configuration>
>         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>         <autoVersionSubmodules>true</autoVersionSubmodules>
>         <preparationGoals>clean install</preparationGoals>
>     </configuration>
> </plugin>
>
> My idea behind this is, that it might be a problem to point to a
> tag-directory within the scm connection. I my understanding those folders
> should be on the same level.
>
> Hope to help
> Stefan
>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Heinecke [mailto:andreas@objectinc.de]
> Gesendet: Donnerstag, 21. August 2008 10:04
> An: users@maven.apache.org
> Betreff: Release fails during SVN commit
>
> Hi there,
>
> I encountered a strange problem. Since a few weeks I'm not able to perform
> a
> release with Maven. The release process fails during executing the
> release:prepare goal at the same position, always. The point at which the
> release fails is when Maven tries to commit the release POM's to SVN. This
> commit fails with the error message that the file which is about to be
> committed already exists at the position in SVN. But it isn't there.
> Strange, uh?
>
> I actually checked the tagbase configuration of the plugin and tried to
> alter it, but the effect remains.
> I don't know what I can try to fix this issue.
> The last thing altered at the configuration is a switch of the SVN server.
> We had to switch to a newer SVN version 1.5.0. We also switched to the new
> 1.5.0 SVN client as we know that there are problems with newer server
> software and older client software.
>
> Please find parts of my pom.xml configuration attached below.
>
> Any pointers are welcome.
>
> Regards,
> Andreas.
>
> My SCM configuration:
> <scm>
>     <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>
>
> <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
> rConnection>
>     <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> </scm>
>
> My release plugin configuration:
> <plugin>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-release-plugin</artifactId>
>     <configuration>
>         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>         <autoVersionSubmodules>true</autoVersionSubmodules>
>         <preparationGoals>clean install</preparationGoals>
>     </configuration>
> </plugin>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19163336.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: AW: Release fails during SVN commit

Posted by David Roussel <na...@diroussel.xsmail.com>.

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-1777868452.commit .
http://svnserver/svn/REPO1/Projects/InstallTools/tags/installer-0.5

also fails if I run it manually, but if I run 'svn up' then rerun it, it
works.

It's as if the previous commit has not updated the working copy in someway.

I tried to reproduce the problem in pure svn commands, creating a new repo,
adding files, tagging, then going back to a previous revision, then tagging
again.  But I was unable to reproduce it.

Perhaps there is a way to get the SCM plugin to log every command it runs,
see which step is not updating the working copy.

Thanks

David



Glase, Stefan wrote:
> 
> 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:
> 
> <scm>
>     <connection>scm:svn:http://xxx/svndir/project/trunk</connection>
>     <developerConnection>scm:svn:http://xxx
> /svndir/project/trunk</develope
> rConnection>
>     <url>http://xxx /svndir/project/</url>
> </scm>
> 
> ...
> 
> <plugin>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-release-plugin</artifactId>
>     <configuration>
>         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>         <autoVersionSubmodules>true</autoVersionSubmodules>
>         <preparationGoals>clean install</preparationGoals>
>     </configuration>
> </plugin>
> 
> My idea behind this is, that it might be a problem to point to a
> tag-directory within the scm connection. I my understanding those folders
> should be on the same level.
> 
> Hope to help
> Stefan
> 
> -----Ursprüngliche Nachricht-----
> Von: Andreas Heinecke [mailto:andreas@objectinc.de]
> Gesendet: Donnerstag, 21. August 2008 10:04
> An: users@maven.apache.org
> Betreff: Release fails during SVN commit
> 
> Hi there,
> 
> I encountered a strange problem. Since a few weeks I'm not able to perform
> a
> release with Maven. The release process fails during executing the
> release:prepare goal at the same position, always. The point at which the
> release fails is when Maven tries to commit the release POM's to SVN. This
> commit fails with the error message that the file which is about to be
> committed already exists at the position in SVN. But it isn't there.
> Strange, uh?
> 
> I actually checked the tagbase configuration of the plugin and tried to
> alter it, but the effect remains.
> I don't know what I can try to fix this issue.
> The last thing altered at the configuration is a switch of the SVN server.
> We had to switch to a newer SVN version 1.5.0. We also switched to the new
> 1.5.0 SVN client as we know that there are problems with newer server
> software and older client software.
> 
> Please find parts of my pom.xml configuration attached below.
> 
> Any pointers are welcome.
> 
> Regards,
> Andreas.
> 
> My SCM configuration:
> <scm>
>     <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>
> 
> <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
> rConnection>
>     <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
> </scm>
> 
> My release plugin configuration:
> <plugin>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-release-plugin</artifactId>
>     <configuration>
>         <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
>         <autoVersionSubmodules>true</autoVersionSubmodules>
>         <preparationGoals>clean install</preparationGoals>
>     </configuration>
> </plugin>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19163336.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

AW: Release fails during SVN commit

Posted by "Glase, Stefan" <St...@opitz-consulting.de>.

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:

<scm>
    <connection>scm:svn:http://xxx/svndir/project/trunk</connection>
    <developerConnection>scm:svn:http://xxx /svndir/project/trunk</develope
rConnection>
    <url>http://xxx /svndir/project/</url>
</scm>

...

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <configuration>
        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
        <autoVersionSubmodules>true</autoVersionSubmodules>
        <preparationGoals>clean install</preparationGoals>
    </configuration>
</plugin>

My idea behind this is, that it might be a problem to point to a tag-directory within the scm connection. I my understanding those folders should be on the same level.

Hope to help
Stefan

-----Ursprüngliche Nachricht-----
Von: Andreas Heinecke [mailto:andreas@objectinc.de]
Gesendet: Donnerstag, 21. August 2008 10:04
An: users@maven.apache.org
Betreff: Release fails during SVN commit

Hi there,

I encountered a strange problem. Since a few weeks I'm not able to perform a
release with Maven. The release process fails during executing the
release:prepare goal at the same position, always. The point at which the
release fails is when Maven tries to commit the release POM's to SVN. This
commit fails with the error message that the file which is about to be
committed already exists at the position in SVN. But it isn't there.
Strange, uh?

I actually checked the tagbase configuration of the plugin and tried to
alter it, but the effect remains.
I don't know what I can try to fix this issue.
The last thing altered at the configuration is a switch of the SVN server.
We had to switch to a newer SVN version 1.5.0. We also switched to the new
1.5.0 SVN client as we know that there are problems with newer server
software and older client software.

Please find parts of my pom.xml configuration attached below.

Any pointers are welcome.

Regards,
Andreas.

My SCM configuration:
<scm>
    <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</connection>

<developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project</develope
rConnection>
    <url>http://xxx.xxx.xxx.xxx/svndir/project</url>
</scm>

My release plugin configuration:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <configuration>
        <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase>
        <autoVersionSubmodules>true</autoVersionSubmodules>
        <preparationGoals>clean install</preparationGoals>
    </configuration>
</plugin>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org