Hello world,

I'm wondering how much of the Maven community uses Confluence as well. I do and I certainly like that.

Some time ago someone Nick Minutello wrote in his blog (can't find the link ATM, sorry) that he is working on a maven plugin that would tranform xdocs into Confuence compatible format and push them onto a server throgh the RPC interface.
The effect - all documentation is viewed and edited through the confluence. Now, what about maven reports which are generated as xdocs? Should they be be pushed up to confluence too? But my projects generates 160 xdocs, totalling over 2.6MB of xml markup. Nah, I don't think so...


Bob McWhirter took an opposite approach. He wrote a perls script (allegedly called "confluenza") that pulls Confluence content down and generates a set of static html pages. You could see the result on http://timtam.codehaus.org/ Notice the "Edit" link at the right bottom corner of the page. J Aaron Farr described it on his blog:
http://www.jadetower.org/muses/archives/000051.html
I pesonally like this approach better than the other on - serving static html is simply faster - but what about my maven reports?!


Therefore I think a combined approach would suit me best. A confluence plugin that would be able to:

1) push my existing xdocs (the hand written ones of course) up to confluence, so that I may edit them online.
This part could be assimilated from Nick's hypothetic (or not?) plugin


2) pull docs from Confluence and turn them into xdocs, so that they get processed by the xdoc plugin and turned into static html. The maven's navigation.xml should also be generated in that proces based on the page parent-child relationships.
Actually, navigation.xml processing would need to become more flexible - I still would like to define vertical toolbar links, and custom menus referncing maven generated reports, the confluence docs should go into a "Documentation" menu, or something.
This is similar to Bob's approach, but would have to be implemented in Jelly, or preferably as a POJO for easy m2 generation, and obviously the output grammar is different.


Too bad that I'm swamped with other work now, so I'm just tossing ideas around... Any takers? I'm willing to do the testing / reviews if someone is willing to work on implementing it.

Rafal



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to