Re: Deploying site to svn repo (google code)
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
Re: Deploying site to svn repo (google code)
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
Re: Deploying site to svn repo (google code)
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 On Mar 26, 2010, at 4:47 PM, Kathryn Huxtable wrote: 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploying site to svn repo (google code)
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
Re: Deploying site to svn repo (google code)
Did you look at wagon-svn?
On Mar 24, 2010, at 12:28 PM, Kathryn Huxtable kath...@kathrynhuxtable.org
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 efficient.
I've tried using the webdav wagon to deploy my site docs, and while
it's okay for individual files, for instance it would be fine to
deploy artifacts, there are *hundreds* of files, mostly javadoc,
associated with my site. It takes forever.
Is there an efficient way to deploy a site to an svn repository?
I tried the scm wagon, using the following in my build section:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-6/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-manager-plexus/artifactId
version1.3/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.3/version
/extension
/extensions
This generated an error on site:deploy as follows:
[INFO] [site:deploy {execution: default-cli}]
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Opened
Uploading: . to scm:svn:https://seaglass.googlecode.com/svn/site/
seaglass
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnecting
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be out-
of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container
[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] = file:/Users/huxtable/.m2/repository/org/apache/maven/
plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] = file:/Users/huxtable/.m2/repository/org/apache/maven/doxia/
doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[2] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[3] = file:/Users/huxtable/.m2/repository/org/apache/maven/doxia/
doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] = file:/Users/huxtable/.m2/repository/xerces/xercesImpl/
2.8.1/xercesImpl-2.8.1.jar
urls[5] = file:/Users/huxtable/.m2/repository/xml-apis/xml-apis/
1.3.03/xml-apis-1.3.03.jar
urls[6] = file:/Users/huxtable/.m2/repository/commons-lang/commons-
lang/2.1/commons-lang-2.1.jar
urls[7] = file:/Users/huxtable/.m2/repository/commons-httpclient/
commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = file:/Users/huxtable/.m2/repository/commons-logging/
commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = file:/Users/huxtable/.m2/repository/commons-codec/commons-
codec/1.2/commons-codec-1.2.jar
urls[10] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] = file:/Users/huxtable/.m2/repository/org/apache/velocity/
velocity/1.5/velocity-1.5.jar
urls[18] = file:/Users/huxtable/.m2/repository/commons-collections/
commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/Users/huxtable/.m2/repository/oro/oro/2.0.8/
oro-2.0.8.jar
urls[20] = file:/Users/huxtable/.m2/repository/org/apache/maven/
shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar
urls[21] = file:/Users/huxtable/.m2/repository/commons-io/commons-io/
1.4/commons-io-1.4.jar
urls[22] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] = file:/Users/huxtable/.m2/repository/org/mortbay/jetty/
jetty/6.1.5/jetty-6.1.5.jar
urls[24] = file:/Users/huxtable/.m2/repository/org/mortbay/jetty/
jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] = file:/Users/huxtable/.m2/repository/org/mortbay/jetty/
servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/usr/local/maven/lib/maven-2.2.1-uber.jar
[INFO]
---
-
[ERROR] FATAL ERROR
[INFO]
---
Re: Deploying site to svn repo (google code)
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
less than one minute. It zips the site up, scp's it to the target, and then
runs an ssh unzip command to unpack the files, then deletes the zip file.
Since I can commit many files at once with subversion, it seems that it ought
to be possible to do something similar with that, though it still may not scale
well.
For the record, my co-developer is fine with the site docs being on my personal
website, but I would prefer that they be with the project domain. I just don't
have ssh access there, and I'm not willing to pay for another hosting site on
my personal provider.
-K
On Mar 24, 2010, at 2:35 PM, Justin Edelson wrote:
Did you look at wagon-svn?
On Mar 24, 2010, at 12:28 PM, Kathryn Huxtable kath...@kathrynhuxtable.org
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 efficient.
I've tried using the webdav wagon to deploy my site docs, and while
it's okay for individual files, for instance it would be fine to
deploy artifacts, there are *hundreds* of files, mostly javadoc,
associated with my site. It takes forever.
Is there an efficient way to deploy a site to an svn repository?
I tried the scm wagon, using the following in my build section:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-6/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-manager-plexus/artifactId
version1.3/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.3/version
/extension
/extensions
This generated an error on site:deploy as follows:
[INFO] [site:deploy {execution: default-cli}]
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Opened
Uploading: . to scm:svn:https://seaglass.googlecode.com/svn/site/
seaglass
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnecting
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be out-
of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container
[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] = file:/Users/huxtable/.m2/repository/org/apache/maven/
plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] = file:/Users/huxtable/.m2/repository/org/apache/maven/doxia/
doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[2] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[3] = file:/Users/huxtable/.m2/repository/org/apache/maven/doxia/
doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] = file:/Users/huxtable/.m2/repository/xerces/xercesImpl/
2.8.1/xercesImpl-2.8.1.jar
urls[5] = file:/Users/huxtable/.m2/repository/xml-apis/xml-apis/
1.3.03/xml-apis-1.3.03.jar
urls[6] = file:/Users/huxtable/.m2/repository/commons-lang/commons-
lang/2.1/commons-lang-2.1.jar
urls[7] = file:/Users/huxtable/.m2/repository/commons-httpclient/
commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = file:/Users/huxtable/.m2/repository/commons-logging/
commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = file:/Users/huxtable/.m2/repository/commons-codec/commons-
codec/1.2/commons-codec-1.2.jar
urls[10] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] = file:/Users/huxtable/.m2/repository/org/apache/velocity/
velocity/1.5/velocity-1.5.jar
urls[18] = file:/Users/huxtable/.m2/repository/commons-collections/
commons-collections/3.2/commons-collections-3.2.jar
urls[19] =
Re: Deploying site to svn repo (google code)
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 kath...@kathrynhuxtable.org
wrote:
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 less than one minute. It zips the site up, scp's it to
the target, and then runs an ssh unzip command to unpack the files,
then deletes the zip file.
Since I can commit many files at once with subversion, it seems that
it ought to be possible to do something similar with that, though it
still may not scale well.
For the record, my co-developer is fine with the site docs being on
my personal website, but I would prefer that they be with the
project domain. I just don't have ssh access there, and I'm not
willing to pay for another hosting site on my personal provider.
-K
On Mar 24, 2010, at 2:35 PM, Justin Edelson wrote:
Did you look at wagon-svn?
On Mar 24, 2010, at 12:28 PM, Kathryn Huxtable kath...@kathrynhuxtable.org
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 efficient.
I've tried using the webdav wagon to deploy my site docs, and while
it's okay for individual files, for instance it would be fine to
deploy artifacts, there are *hundreds* of files, mostly javadoc,
associated with my site. It takes forever.
Is there an efficient way to deploy a site to an svn repository?
I tried the scm wagon, using the following in my build section:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-6/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-manager-plexus/artifactId
version1.3/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.3/version
/extension
/extensions
This generated an error on site:deploy as follows:
[INFO] [site:deploy {execution: default-cli}]
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Opened
Uploading: . to scm:svn:https://seaglass.googlecode.com/svn/site/
seaglass
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnecting
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be out-
of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container
[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] = file:/Users/huxtable/.m2/repository/org/apache/maven/
plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/
doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[2] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[3] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/
doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] = file:/Users/huxtable/.m2/repository/xerces/xercesImpl/
2.8.1/xercesImpl-2.8.1.jar
urls[5] = file:/Users/huxtable/.m2/repository/xml-apis/xml-apis/
1.3.03/xml-apis-1.3.03.jar
urls[6] = file:/Users/huxtable/.m2/repository/commons-lang/commons-
lang/2.1/commons-lang-2.1.jar
urls[7] = file:/Users/huxtable/.m2/repository/commons-httpclient/
commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = file:/Users/huxtable/.m2/repository/commons-logging/
commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = file:/Users/huxtable/.m2/repository/commons-codec/commons-
codec/1.2/commons-codec-1.2.jar
urls[10] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] =
Re: Deploying site to svn repo (google code)
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 Mar 24, 2010, at 12:41 PM, Kathryn Huxtable kath...@kathrynhuxtable.org
wrote:
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 less than one minute. It zips the site up, scp's it to
the target, and then runs an ssh unzip command to unpack the files,
then deletes the zip file.
Since I can commit many files at once with subversion, it seems that
it ought to be possible to do something similar with that, though it
still may not scale well.
For the record, my co-developer is fine with the site docs being on
my personal website, but I would prefer that they be with the
project domain. I just don't have ssh access there, and I'm not
willing to pay for another hosting site on my personal provider.
-K
On Mar 24, 2010, at 2:35 PM, Justin Edelson wrote:
Did you look at wagon-svn?
On Mar 24, 2010, at 12:28 PM, Kathryn Huxtable kath...@kathrynhuxtable.org
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 efficient.
I've tried using the webdav wagon to deploy my site docs, and while
it's okay for individual files, for instance it would be fine to
deploy artifacts, there are *hundreds* of files, mostly javadoc,
associated with my site. It takes forever.
Is there an efficient way to deploy a site to an svn repository?
I tried the scm wagon, using the following in my build section:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-6/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-manager-plexus/artifactId
version1.3/version
/extension
extension
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.3/version
/extension
/extensions
This generated an error on site:deploy as follows:
[INFO] [site:deploy {execution: default-cli}]
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Opened
Uploading: . to scm:svn:https://seaglass.googlecode.com/svn/site/
seaglass
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnecting
scm:svn:https://seaglass.googlecode.com/svn/site/seaglass - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be out-
of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container
[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] = file:/Users/huxtable/.m2/repository/org/apache/maven/
plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/
doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[2] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[3] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/
doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] = file:/Users/huxtable/.m2/repository/xerces/xercesImpl/
2.8.1/xercesImpl-2.8.1.jar
urls[5] = file:/Users/huxtable/.m2/repository/xml-apis/xml-apis/
1.3.03/xml-apis-1.3.03.jar
urls[6] = file:/Users/huxtable/.m2/repository/commons-lang/commons-
lang/2.1/commons-lang-2.1.jar
urls[7] = file:/Users/huxtable/.m2/repository/commons-httpclient/
commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = file:/Users/huxtable/.m2/repository/commons-logging/
commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = file:/Users/huxtable/.m2/repository/commons-codec/commons-
codec/1.2/commons-codec-1.2.jar
urls[10] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] = file:/Users/huxtable/.m2/repository/org/apache/maven/
doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] = file:/Users/huxtable/.m2/repository/org/codehaus/plexus/
plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16]
Re: Deploying site to svn repo (google code)
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
Re: Deploying site to svn repo (google code)
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
