sebastien wrote: it can be interesting to generate documentation for other documentation systems like doxygen for example. So why not define a base interface named DocumentationGenerator with method like getClassifierDocumentation, getMethodDocumentation, getParameterDocumentation and so one, and then a JavaDocGenerator that would implement this interface and called from the templates. That way, we would not have to modify getDocumentation and all the templates that still use this method would not make the tests fail. And we would keep documentation generation in one place in order to be able to update it (e.g. as javadoc specification evolves) or extend it (e.g. with a doxygen generator).
I know it might seem a bit "too much" but I think it would be a really interesting feature, to be able to edit documentation in the UML model, without caring about the syntax of a particular documentation system. (end of quote) yeah it's definitely worth the effort, can you write something that will work (+ junit tests) ? then we'll take a look at applying it to the codebase together with the other AndroMDA developers that are interested thanks for all the efforts so far! -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2067#2067 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
