Hi Hervé, >> 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]
we (thats the logging project) use "mvn site" for our docs and currently we have at least one weird process which is scp'ing the docs to localhost. From there it is committed to svn and from there we run "svn up". This is true for one project, the others have different processes. That being said, we have not had a vote on that, but it seems that the majority of us doesn't want to use the CMS directly. Therefore we were initially looking for a mvn based solution. Did I understand you correct that the "main site" should be cared on CMS level while for example API docs are updated with m-scm-publish? Why can't we use mvn site together with m-scm-publish? >> What is left to leave sandbox? > 1. interest/feedback Interest!! :-) > 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 Well, we need to clean up our release process. We are not ready for the svnpubsub requirement. Therefore we are looking at this plugin. > 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. We are not one of these cases, luckily. > 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" would look nice, but I am really not looking for pure beauty. I would be glad to solve our problems first, then look for beauty. > 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 Cool, thanks for your help. We are speaking of logging.apache.org. Inside are several components, like log4j1, the brandnew log4j2 which is blocked by the site release process, log4php, log4net and so on. The biggest problem is log4j1 and another urgent one is log4j2. We have the recommendation to use ASF CMS but so far we would prefer to use maven only solutions. All projects are independent, no parent project. We have a main site which links to the several subprojects. One of the ideas which is currently in place is to "do something with maven" which commits to a svn repos which is read by svnpubsub. The repos could look like: /$asfrepos/logging/pubsub/logging/index.html --> main site /$asfrepos/logging/pubsub/logging/log4j/index.html --> logj41 site /$asfrepos/logging/pubsub/logging/log4j2/index.html --> logj42 site and so on. What do you think about that? > 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 Sure! Thanks again! I feel a little bit lost and your help is highly appreciated. Christian > >> >> Thanks! > somebody interested, nice! > > 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] > -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
