In my mind using SOAP (or XML RPC) is the best way as well, as this
will give maximum portability. For instance at some later date
Confluence may become available on Apache servers. With SOAP, all we
need to do is to change the server URL. If we get all docs in XML, we
may reuse parts of the existing HTML rendering Velocity template to
give the docs more "branded" look.
Andrus
On Mar 24, 2006, at 6:43 AM, Cris Daniluk wrote:
I'm slowly working on the doc plugins, etc. The real issue is actually
getting Confluence to properly compile from source, more than
anything. I
may just use the SOAP API to bypass Confluence. Then we can even
include it
in the ant build scripts.
Cris
On 3/23/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
I am in the process of creating the M12 release. All major things are
in. Now I am testing it on various databases and fixing db-specific
issues.
I thought we could ship the docs from Wiki with M12, but the PDF
export is too unorganized (chapters are sorted alphabetically by name
- very confusing). Postponing the doc system switch till beta (I'll
probably open a Jira task to track progress on that).
Almost there....
Andrus
