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.googlecode.com/svn/doc/index.html for what it looks like. Unfortunately, the "/index.html" is necessary. I have no objection to timestamps, by the way, but I figured that random doc fixes that didn't change the version would have fewer changes that way. -K On Mar 26, 2010, at 4:02 PM, Brian Fox wrote: > Maybe we should just turn on site hosting @ oss.sonatype.org in Nexus.... > > 2010/3/25 Kathryn Huxtable <kath...@kathrynhuxtable.org>: >> 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, *.gif, and *.jpeg files (at least) to their appropriate mime types. >> >> For each release, generate your site docs and then rsync them to the >> "myproject-site" directory. This should be committable in a reasonable time >> frame. Doing an rsync where files get deleted should make sure that the >> files in the svn repo are always clean. >> >> The biggest disadvantage I see to this is that Google Code doesn't display >> the index.html file in a directory when you browse to the directory, and why >> should it? It's a subversion repo, not a web page server. So you have to add >> the "/index.html" to your site docs in references to directories, including >> the top-level directory. >> >> I've deployed this the first time and it seemed to work. I haven't tried >> changes yet. >> >> It looks as if GitHub has a nicer built-in solution, though it has some >> issues... >> >> Anyway, there's no reason an svn wagon couldn't do something like this. But >> the one on java.net took forever. It looked as if each file was a separate >> commit. >> >> I did my initial commit via Eclipse, and while it took quite a bit longer >> than using the ssh wagon, it was just a few minutes. Not hours, as with the >> svn wagon. >> >> Any comments? Given the number of code hosting sites without ssh access, >> this seems like an area for further development. >> >> -K >> >> On Mar 24, 2010, at 4:59 PM, Kathryn Huxtable wrote: >> >>> 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 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-svn-repo-%28google-code%29-tp28020109p28021955.html >>>> Sent from the Maven - Users mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
