Soon is going to be a year since we moved Confluence in as our "cwiki". At that
time we were using version 0.13 of the plugin. Today we are using a 0.14 beta version
that addresses some of the initial issues, but not all.
Some of the issues I think stand in our way are:
- Plugin wont update exported pages that have content dynamically created by
other macros ({children} or {toc} for example)
- Plugin wont update attachments in the HTML version when these are modified on
the Confluence side.
- Plugin wont rename (or allow you to delete) HTML versions when the Confluence
page name changes.
- In the exported HTML, all Confluence native content (images like the check
boxes) still point as absolute links to the cwiki base URL. So, the exports are
not totally complete/self-contained.
- Some reference to Confluence data (dynamic links) get also translated as
absolute links pointing to the cwiki base URL. Similar case as the one just
described above.
- Some Confluence macros (thumbnails for example) just don't get translated
right and wont work properly in the exported HTML version.
- There are some issues with JIRA integration too (like dynamic content update
and missing images)
I would personally prefer to get these sorted out before we move on.
Cheers!
Hernan
Jason Dillon wrote:
On Feb 13, 2007, at 2:44 PM, Hernan Cunico wrote:
used for the main
site, i think that redirecting is a bad idea as we want to keep the
url in
geronimo.apache.org.
Totally agree, but we are not using Confluence for the site yet. I was
bringing that up as a temp solution till we fix the autoexport plugin
issues and move full steam forward to authoring all sites (main and
subprojects) with Confluence. Never mind, I wont be surfacing that
idea again ;-)
Hernan, I think that the plugin works fine to move forward... OpenEJB,
ActiveMQ, XBean, and several others are using it w/no significant
problems. Yes I know there are a few issues, but we can fix them
*after* we move, I don't see those problems as blocking.
--jason
