tag:blogger.com,1999:blog-27773736.post4627545857675483758..comments2021-11-23T18:17:56.007+01:00Comments on Too Loud a Solitude: Release issue...Emmanuel Lécharnyhttp://www.blogger.com/profile/00606458715529159834noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-27773736.post-19219139764348593532011-06-22T12:14:16.872+02:002011-06-22T12:14:16.872+02:00Its because of the eu mirror of svn. If you use th...Its because of the eu mirror of svn. If you use the svn master you will see that you not get this at all.Norman Maurernoreply@blogger.comtag:blogger.com,1999:blog-27773736.post-45179499116460047512011-06-22T00:59:28.781+02:002011-06-22T00:59:28.781+02:00@Larry If it were an issue with SVN, wouldn't ...@Larry If it were an issue with SVN, wouldn't have such an issue more frequently, as I'm committing quite often (average, three times a day), no ?<br /><br />@Nicolas, @Chris, sounds like a valuable explanation. The :<br />- svn ci tags on US server<br />- svn up from EU server<br />- commit something with the latest revision <br />sequence sounds like a good candidate for the kind of error I get.<br /><br />Now, I have no idea why the release plugin uses the release number in the process. IMO, it has a perfect knowledge on what has been committed - or not- and should not do a svn up at all.<br /><br />Or may be I'm just wrong...<br /><br />Anyway, thanks all of you for your feedback, I feel less lonely :)Emmanuel Lécharnyhttps://www.blogger.com/profile/00606458715529159834noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-31970202685155753552011-06-21T22:01:45.722+02:002011-06-21T22:01:45.722+02:00Following up on this for anyone searching, I also ...Following up on this for anyone searching, I also think using https://svn.us.apache.org for your scm url will work.Chris Custinehttps://www.blogger.com/profile/06441112084698340779noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-72350332433058546272011-06-21T21:57:42.488+02:002011-06-21T21:57:42.488+02:00This is probably the known issue of using the EU a...This is probably the known issue of using the EU apache SVN mirror. There is a bit of info about it here: http://www.apache.org/dev/version-control.html#https-svn-config<br /><br />Seems the easiest way is to wait a few seconds and try the command again (after it has sync'd) but I also wonder if you could point the scm to the US server directly? HTHChris Custinehttps://www.blogger.com/profile/06441112084698340779noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-28216449011604825082011-06-21T20:04:03.532+02:002011-06-21T20:04:03.532+02:00This is probably due to the european mirror of the...This is probably due to the european mirror of the Apache svn. Just after a commit on that server, a checkout or an update at the just committed revision is not available right away. There is some lag due to the synchronisation between the svn master in the US and the mirror in EU.<br />I faced the same issue while trying to use the mercurial/svn bridge on the apache svn server. The fix I did (and which should probably be done in maven too), was to do a regular check that the expected revision exists, every second during few seconds, then either actually fail or actually do the checkout/update.Nicolas Lalevéehttps://www.blogger.com/profile/17580003738884443701noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-55326675523157995732011-06-21T19:37:17.418+02:002011-06-21T19:37:17.418+02:00See:
http://weblogs.java.net/blog/johnsmart/archi...See: <br />http://weblogs.java.net/blog/johnsmart/archive/2008/12/subversion_mave.html<br /><br />And: http://jira.codehaus.org/browse/MRELEASE-427<br /><br />It is with Subversion clients 1.5.0 or higher.Anonymoushttps://www.blogger.com/profile/18326035072015488941noreply@blogger.com