2012/8/30 Olivier Lamy <[email protected]>: > Hi, > > 2012/8/30 Simone Tripodi <[email protected]>: >> Salut Luc, >> >>> These are good news. Would we be able with this setting to go to svnpubsub? >> >> yes they will work, skin and SCM publishing are unrelated stuff - >> Olivier Lamy, which is also commons committer, already did the job for >> Apache DirectMemory via a new mvn plugin called scm-publish, hopefully >> we can provide us a guideline. >> >> I will invite him to publicly explain us how to manage the SvnPubSub. > Yup this plugin works (and you can simply use as today mvn site-deploy > for a single module build :-) ) > I tested that for directmemory.a.o and archiva.a.o > Note the archiva is a bit more complicated as it included more than > one reactor but some sub site. > But in the commons case I would recommend something similar we are > testing for maven site > Note this site include a lot of sub site (versionned plugins > documentation, shared components, scm etc...) > But if using the plugin for svnsubpub this means checkout too much > content for just deploying a plugin site. > See > olamy@minotaur:~$ du -sh /www/maven.apache.org > 6.3G /www/maven.apache.org > olamy@minotaur:~$ du -sh /www/commons.apache.org > 2.3G /www/commons.apache.org > > So we are trying a mixed solution :-) (branch: > http://svn.apache.org/repos/asf/maven/site/branches/INFRA-4466/trunk/). > The main site is build tru cms (a buildbot job run maven site plugin > and push content then we can publish to live: > http://maventest.apache.org). > The sub sites are deployed using the scmpub sub plugin. To avoid > pubsub to delete those sub parts (because there are not generated via > buildbot job), we worked with infra for configuring subpath to not > delete in a file called expath.txt > (http://svn.apache.org/repos/asf/maven/site/branches/INFRA-4466/trunk/content/resources/extpaths.txt) > > This plugin is in maven sandbox > (http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-scm-publish-plugin/). Just moved out of sandbox: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-scm-publish-plugin/ > Quick explanation of how that works: > * checkout (by default) or update of the target svnpub path to a local > directory > * list all files from the original and the new deployed site directory > * compare both content > * scm add for new files, scm delete for deleted files > * copy files from deployed site directory to directory with checkout > content (fix possible line ending issues) > * checkin > * et voilà > > I'm satisfied by how that works today :-) I will probably release a > first version next week (as I need that for releasing archiva) before > I will test that works with github for gh pages site. > > Let me know if you need more details. > >> >> Thanks! >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy
-- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
