2013/4/22 Rene Gielen <rene.gie...@gmail.com>: > I'm not too sure that this is a net win in the end, though I see the > (big) itch you want to scratch. We introduced the Javadoc snippets to > remove duplication on documentation. I'm pretty sure that most users > really appreciate that our Javadocs contain really deep information > including examples. Also, it is much easier for a contributor to > steadily follow a "write code with docs" workflow rather than "write > code and please don't forget to write / align docs in wiki".
I'm quite often noticing that the docs are out of sync with implementation, even if they are embedded in the source code vide CompositeActionMapper. The second thing is a look which basically doesn't look good when docs are included via snippet - nor formatting neither code links work. Another think is karma, we can easily grant access to wiki, just iCLA is needed, access to repo requires more steps - first is commitment :-) > That said, I'm sometimes wondering if Confluence is the best way to go > for maintaining our docs - putting aside how painful a migration could > be. Looking over to Wicket land, where the docs are maintained as > wiki-like markup templates which get expanded and deployed with the > project build seems to be really straightforward and gives better > control of such things like snippets... Maybe you are right but I'm not so sure ... Do you have any link or more info about Wicket-way? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
