CMS uses SVN but is not the same thing. I think there are 3 ways to publish a site:
svnpubsub - i.e. generate and upload site to the appropriate SVN tree and it will automatically get published This is what Commons uses currently CMS + svnpubsub: This uses CMS to maintain the site; after editting the site using CMS it is automatically built to a staging area which can then be published. This is what the www.apache.org site uses (though one can also edit/publish manually). It won't work for Commons because of the multiple sub-sites. gitpubsub - AFAIK this is the same as svnpubsub but using Git On 15 September 2016 at 20:21, Ralph Goers <[email protected]> wrote: > I migrated Log4j to the CMS because Infra basically said it was the only > supported way to publish an ASF web site. Has that changed? Is there a new, > documented way to use git for that? > > Ralph > >> On Sep 15, 2016, at 2:42 AM, Jochen Wiedmann <[email protected]> >> wrote: >> >> On Thu, Sep 15, 2016 at 11:23 AM, Stian Soiland-Reyes <[email protected]> >> wrote: >>> Commons is special in that we have many components within the same website, >>> but update them separately and generally only at release time. >>> >>> With git you would always need to check out all of the commons site, e.g. >>> lots of javadoc for each of the components. We might have to fix the site >>> deploy so it then correctly updates the right subfolder there. >>> >>> On the other side, adding lots of files is tremendously faster with git. :) >>> >>> Or are you also proposing to move to a single commons-site project with >>> buildbot and then add folders there manually rather than with mvn >>> site:site-deploy? >> >> Certainly not. On the contrary, I'd like to simplify work for the components. >> >> Jochen >> >> >> -- >> The next time you hear: "Don't reinvent the wheel!" >> >> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
