Le dimanche 20 mai 2012 14:23:59 Christian Grobmeier a écrit : > Hello folks, > > what is the state of the maven-site-scm-publish plugin? > > As I could understand, it checks out a specific svn repository path, > diffs/merges it with my locally generated site, and then commits it > back to the specific repository. This is basically what apache > projects could need with svnpubsub. exactly notice that if you have unversioned site like maven site (not plugins or whatever component for which documentation is published only during release), we're directly using CMS (with its bookmarklet) to automatically publish content at each commit, without the m-scm-publish-p: see [1]
> > Is the plugin already working? yes, I used it to inject 10 plugin documentation histories [2] with great success. Notice it caused a great load on commit mailing list (tens if not hundreds MB), then I'll have to work with infra IMHO when I import actual 5GB of data... > What is left to leave sandbox? 1. interest/feedback 2. time, since I'm actually working on plugin-tools interest/feedback is the most lacking, because the plugin is in a point where it is working pretty well, but not easy to use in real world, since svnpubsub has consequences on release practices. I made a proposal on [3], asked for feedback, but got none for the moment I'm not fully happy for the moment, since there are much command-line for release process, independently from the pure svnpubsub. There is only one known "hard" limitation I know of for the moment: in the case of a multi-module project publishing content not only in a single directory but in multiple (like surefire or plugin-tools, which have their root directory but also some directory under /plugins/), committing staged content in svn won't work at all. But that case is rare, and we could propably change their structure to work more like archetype on future releases. Ideally, I'd like to improve wagon-scm directory support, to commit whole directory content in one commit (without suppressing modules content), then integrate maven-site-plugin conveniently since you could simply use a scm url in distributionManagement. That won't change the release process question but at least ease usage: "mvn - Preporting site-deploy" for the moment, I just published latest documentation: [4] (sync pending...) tel me what project/component you want to migrate to svnpubsub and we can work toward this precise case > > Thanks! somebody interested, nice! And hopefully you'll have projects with less content than Maven itself, because Maven migration to svnpubsub is really a big task: I'd be happy to start with smaller content Regards, Hervé > Christian [1] http://maventest.apache.org/ [2] https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/ [3] http://maventest.apache.org/developers/release/maven-plugin-release.html [4] http://maven.apache.org/sandbox/plugins/maven-scm-publish-plugin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
