Re: Deploying site to svn repo (google code)

2010-03-26 Thread Kathryn Huxtable
Oh, I should add that I thought better about rsync. Instead I made my site deploy location be a file:/// pointing to my checked out site docs. I don't think that has the nice effect that the SSH wagon does of wiping the previous contents, but there are ways... That's why Larry invented Perl. -K

Re: Deploying site to svn repo (google code)

2010-03-26 Thread Kathryn Huxtable
That would be up to you, but you're not the hosting site. You're just a way-station on the way from Google Code to Central. My solution works, by the way. I deployed another release, having turned off timestamps in the javadocs. I then committed that and all is well. See http://seaglass.googlec

Re: Deploying site to svn repo (google code)

2010-03-26 Thread Brian Fox
Maybe we should just turn on site hosting @ oss.sonatype.org in Nexus 2010/3/25 Kathryn Huxtable : > Okay, here's a somewhat manual solution: > > Before doing anything else, create a "site" branch in your subversion > repository and check it out into a directory outside your project's > dire

Re: Deploying site to svn repo (google code)

2010-03-25 Thread Kathryn Huxtable
Okay, here's a somewhat manual solution: Before doing anything else, create a "site" branch in your subversion repository and check it out into a directory outside your project's directory, say "myproject-site". Set the auto-props in your subversion config file to set *.html, *.css, *.png, *.g

Re: Deploying site to svn repo (google code)

2010-03-24 Thread Kathryn Huxtable
Yes, there's that, but I was willing to write something that set those after the fact. -K On Mar 24, 2010, at 4:56 PM, lukewpatterson wrote: > > > justinedelson wrote: >> >> Did you look at wagon-svn? >> > > wagon-svn would be great but it doesn't support mime-type auto-props, which > is cr

Re: Deploying site to svn repo (google code)

2010-03-24 Thread lukewpatterson
justinedelson wrote: > > Did you look at wagon-svn? > wagon-svn would be great but it doesn't support mime-type auto-props, which is crucial for site deployment https://wagon-svn.dev.java.net/issues/show_bug.cgi?id=4 -- View this message in context: http://old.nabble.com/Deploying-site-to-s

Re: Deploying site to svn repo (google code)

2010-03-24 Thread Kathryn Huxtable
Thanks! I'll stick with my personal site for now. -K On Mar 24, 2010, at 2:52 PM, Justin Edelson wrote: > My experience was that wagon-svn was faster than dav, but they both > are sub-par compared with scp because there's no way to remotely > execute a command (I.e. unzip). > > Justin > > On Ma

Re: Deploying site to svn repo (google code)

2010-03-24 Thread Justin Edelson
My experience was that wagon-svn was faster than dav, but they both are sub-par compared with scp because there's no way to remotely execute a command (I.e. unzip). Justin On Mar 24, 2010, at 12:41 PM, Kathryn Huxtable wrote: > Yes, I did. It works fine for deploying artifacts, as there are > u

Re: Deploying site to svn repo (google code)

2010-03-24 Thread Kathryn Huxtable
Yes, I did. It works fine for deploying artifacts, as there are usually only a few. When deploying a site, though, it doesn't scale well. It deploys each file separately, or at least the last version I tried did. It took hours. I don't consider that reasonable when the wagon-ssh deploys in les

Re: Deploying site to svn repo (google code)

2010-03-24 Thread Justin Edelson
Did you look at wagon-svn? On Mar 24, 2010, at 12:28 PM, Kathryn Huxtable wrote: > My project is hosted at Google Code, and I'm syncing to Central via > Sonatype. > > I've been deploying my site documentation to my personal website > because I have ssh access there and the ssh wagon is very effi