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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 1:43 PM To: 'Maven Users List' Subject: AW: AW: Release fails during SVN commit As the discussion pointed by Emmanuel shows the root of the problem is the SVN 1.5.1 client software. I can't say if it is a bug or a changed behaviour, refer to 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:[EMAIL PROTECTED] Gesendet: Donnerstag, 21. August 2008 16:46 An: Maven Users List Betreff: Re: AW: Release fails during SVN commit If it's happening directly from the command-line as Daniel indicated (I haven't tried it myself, but as far as I know Maven uses the command-line, not JavaHL), then it can't be a JavaHL issue. -Stephen On Thu, Aug 21, 2008 at 10:38 AM, Emmanuel Venisse < [EMAIL PROTECTED]> wrote: > The issue is discussed on the subversion users list : > > http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html > > It is related to a change in JavaHL: > * correctly set the peg revision for copy in JavaHL (r31994) > > Emmanuel > > On Thu, Aug 21, 2008 at 4:15 PM, Daniel Kulp <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> > 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:[EMAIL PROTECTED] > > > > > 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 > > > > > > > > <[EMAIL PROTECTED]>wrote: > > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each > of > > > > > > > > these > > > > > > > > > > platforms. > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > > > > Von: Luke Daley [mailto:[EMAIL PROTECTED] > > > > > > Gesendet: Donnerstag, 21. August 2008 11:12 > > > > > > An: Maven Users List > > > > > > Betreff: Re: Release fails during SVN commit > > > > > > > > > > > > If your on Mac OS 10.5, 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: [EMAIL PROTECTED] > > > > > > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > > > > > > > > > > > LD. > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > > > > Daniel Kulp > > > > [EMAIL PROTECTED] > > > > http://www.dankulp.com/blog > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > > Daniel Kulp > > [EMAIL PROTECTED] > > http://www.dankulp.com/blog > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
