I don't know how often we'd want to build the site... maybe once per release. But I don't see a problem adding it to the "content" section of CMS, in a version-specific subdirectory (like: maven-site/<release-version>). I don't think there's much risk of accidental publication, especially since we don't (yet) have links to navigate there.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, Feb 27, 2013 at 12:15 PM, Benson Margulies <[email protected]> wrote: > I don't think either. > > What the plugin does, at site-deploy, is to make a checkout of a > separate SCM URL (presumably part of the site content tree), put the > output of the site plugin in there, and check it in, thus publishing > it as part of the web site content. > > On Wed, Feb 27, 2013 at 12:12 PM, David Medinets > <[email protected]> wrote: >> does this imply that the site directory will become part of the >> repository or will 'site' be ignored by svn? >> >> On Wed, Feb 27, 2013 at 2:02 PM, Benson Margulies <[email protected]> >> wrote: >>> Under ACCUMULO-1122, I'm fixing up things so that >>> >>> 'mvn site' >>> >>> will push the maven-generated content to someplace in the svn tree >>> that the SCM looks at. >>> >>> I'm currently running a test-run that will deliver to >>> >>> https://svn.apache.org/repos/asf/accumulo/site/trunk/maven-site. >>> >>> Note the lack of 'content' to avoid accidental publication. >>> >>> Once it's up there, I'll let people know, and we can decide if we want >>> to make this real.
