Hi Oleg!!! > On the other hand - I remember trying to push the generated site directly to > the svn using both wagon-svn and maven-svn-wagon and in the end I decided to > generate the new site on the local filesystem instead and then manually > checkout old site, overwrite it with the generated files and manually commit > the modified version back.
that is exactly what we do in Cocoon, it's not what I really like (because requires extra manual steps) but at least it should work :) All the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Thu, Jan 19, 2012 at 9:12 AM, Oleg Estekhin <oleg.estek...@gmail.com> wrote: > Hi > > **shameless self-advertisement, sorry** > You can try my com.google.code.maven-svn-wagon: maven-svn-wagon (dev site at > http://code.google.com/p/maven-svn-wagon/, the artifact is available from > the Central). In general it works just as the Kohsuke's > org.jvnet.wagon-svn:wagon-svn, and it depends in the SVNKit too, but it > should work just a little bit better. > > On the other hand - I remember trying to push the generated site directly to > the svn using both wagon-svn and maven-svn-wagon and in the end I decided to > generate the new site on the local filesystem instead and then manually > checkout old site, overwrite it with the generated files and manually commit > the modified version back. I don't remember right now what it was exactly > that I did not liked when autodeploing the site directly to the svn, the > only glitch I remember is that site goal generates some files with mixed > ending style (both lf and crlf in some files, this glitch is still present) > and if you have configured the svn:eol-style autoproperty for html files > then it will break the build. > > -----Исходное сообщение----- From: Simone Tripodi > Sent: Wednesday, January 18, 2012 11:39 AM > To: Maven Developers List > Subject: Re: deploy maven site on SVN > > > Hi all! > > thanks for the feedbacks - we are using indeed the Kohsuke's wagon but > to deploy to ASF svn space it takes almost 3secs/page (it could be an > issue of my ADSL upload band) but since javadoc is really big, it > takes too much time :( > > wagon-ssh is still the faster :) > > all the best, have a nice day! > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > > On Wed, Jan 18, 2012 at 2:13 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: >> >> if the deps are cat a/b i can see about getting kk to donate the code >> here... but i think it uses svnkit so probably out of luck. (kk is an asf >> committer on one of the commons projects, so cla on file) >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, random nonsense >> words and other nonsense are a direct result of using swype to type on the >> screen >> On 18 Jan 2012 00:27, "Brett Porter" <br...@apache.org> wrote: >> >>> wagon-svn by Kohsuke is much faster, but both should work. >>> >>> Either way, I think the main thing we need to do is make sure repeated >>> identical executions of the site don't change files needlessly, so that >>> the >>> upload is minimal. >>> >>> On 18/01/2012, at 7:04 AM, Olivier Lamy wrote: >>> >>> > 2012/1/17 Simone Tripodi <simonetrip...@apache.org>: >>> >> Hi all guys, >>> >> ASF requirements for new incubating podlings requires that sites are >>> managed >>> >> >>> >> * via the SCM >>> >> * via svnpubsub >>> >> >>> >> At Apache Any23 we want to keep the mvn generated site for clear >>> >> reasons - the problem is that using a 3rd part ftp-wagon the deploy >>> >> procedure is slooooooooooooow and takes too much time :S >>> > >>> > Agree that wagon scm is slow >>> > (http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html) >>> > as it's a per file deploy/commit. >>> > >>> >> >>> >> Can you suggest us please an automated site-deploy procedure using mvn >>> >> - that doesn't involve manual steps? >>> >> A turnaround would be svn checking out the target dir, deploying the >>> >> site there, then committing, but I don't think it is a friendly >>> >> procedure... >>> > I don't see better solution :-( >>> >> >>> >> Many thanks in advance, all the best!!!! >>> >> -Simo >>> >> >>> >> http://people.apache.org/~simonetripodi/ >>> >> http://simonetripodi.livejournal.com/ >>> >> http://twitter.com/simonetripodi >>> >> http://www.99soft.org/ >>> >> >>> >> --------------------------------------------------------------------- >>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> >> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >>> > >>> > >>> > >>> > -- >>> > Olivier Lamy >>> > Talend: http://coders.talend.com >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> > For additional commands, e-mail: dev-h...@maven.apache.org >>> > >>> >>> -- >>> Brett Porter >>> br...@apache.org >>> http://brettporter.wordpress.com/ >>> http://au.linkedin.com/in/brettporter >>> http://twitter.com/brettporter >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
