On 12-12-26 04:50 AM, Mick Semb Wever wrote: > >> Please share your thoughts on this proposition. >> If nobody commented before Dec 25, I will then proceed with the above >> plan in order to meet the deadline of Dec 31. >> >> Thank you all for your attention. > > In a the middle of xmas session i was a little slow on this. > Dec 25 has past and everything you're written looks excellent! > > Some questions… > > Will it be and at what address would the staging website be visible at?
None, unless you checkout site/staging to some web server at localhost. Is that a problem? > Will site/publish/ and site/staging/ always include all 4 > parts (tiles-site, tiles-autotag, tiles-request and tiles-parent)? Site/publish and site/staging would contain what is currently published at tiles.apache.org. > The idea is that any release of any of the projects will commit to > site/staging/ ? mvn site-deploy would do exactly that. > Will this mean that updates to tiles.apache.org can only be done via > releases? Manual commits are also possible (for archiving old documentation during a major release for instance, svn mv framework 2.2/framework). maven-scm-publish-plugin works by checking out the current site into a local directory, copying the new files into that location, and committing again. It doesn't remove anything as far as I can tell.
