Then I don't understand the problem. We can move a whole bunch of pages in a single click. For example, the "Components List" [1] page contains a lot of children pages related to components. We can MOVE it AND ALL ITS CHILDREN to the SMXCOMP space in a single click. If find this much easier than exporting the space, reimporting it in a new space (this is a real pain by itself and can not be done without a lot of hacking of the exported xml to change all the references to the space) and pruning the two spaces to avoid having the same page on both.
[1] http://cwiki.apache.org/confluence/display/SM/Components+list On Wed, Jun 4, 2008 at 6:54 PM, Bruce Snyder <[EMAIL PROTECTED]> wrote: > On Wed, Jun 4, 2008 at 9:37 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> The downside of using a single space is that you can not have two >> pages with the same name in the whole space. >> I guess we will need such duplicate pages for "Building", "Source" and >> pages that apply to all of the subprojects while they need a somewhat >> different content. > > I agree completely - that's a problem. Which is exactly why I was > trying to export the existing SM wiki to create a SMX3 wiki. I'm not > suggesting that we use a single wiki space at all. > > > Bruce > -- > perl -e 'print unpack("u30","D0G)[EMAIL > PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > );' > > Apache ActiveMQ - http://activemq.org/ > Apache Camel - http://activemq.org/camel/ > Apache ServiceMix - http://servicemix.org/ > Apache Geronimo - http://geronimo.apache.org/ > > Blog: http://bruceblog.org/ > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
