Hello. [Sorry for jumping into the discussion while missing the meaning of most of what is being said (and cutting it).]
> [...] > > So why cause additional work for projects that no longer use the CMS? > > I repeat, projects hopped on to the SVN area of the CMS , that is unsupported > and should not have been allowed to happen, it was a workaround by projects > undocumented to support mainly javadocs etc from what I gather. > > You caused the additional work yourselves in the beginning by not fully > removing > from the CMS and all its infrastructure. Infra wants to clear out that area > as part > of migrating away and provides a new space. >From what I recollect, each of the "Commons" projects (component) has its own "trunk" area that is now a "git" repository. "trunk" contains a sub-directory under SVN named "site-content".[1] For quite some time now, the only thing I'm doing with this directory is along the following: $ mvn site site:stage $ cd site-content $ rm -rf * $ cp -r ../target/staging/* . ["svn add" for added files, "svn del" for removed files...] $ svn commit And the web site for that component was updated. Is "site-content" being replaced by another location? Is the consequence that in each component we'll have to $ svn co https://new_location_of_site_content site-content ? Could we perhaps take this opportunity to do away with SVN and "site-content" and have some "mvn" target directly populate the web site? Regards, Gilles [1] This has always seemed like a kludge and has repeatedly caused issues (some of which have been worked around in the POM, IIRC). --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
