Developer's Diary
Software development, with Terry Ebdon
|
I'd like to use Doxygen for my Groovy code, but it's not Groovy aware. The Groovy install includes GroovyDoc, which is a Groovy aware clone of JavaDoc. But JavaDoc and GroovyDoc seem very basic when compared to Doxygen.
GroovyDoc does not use markdown, but does allow HTML. I could translate my existing markdown comments into HTML, but it's not a nice way to work.
My large comment blocks, mainly in file / class headers, could be moved into a Doxygen project. This would be the product, design and user documentation.
GroovyDoc would document the implementation details.
But how do I link the two projects together? If I can generate Doxygen style tag files from the GroovyDoc output that would get me half-way there. Ideally I'd like an easy way to link back from GroovyDoc to Doxygen as well, without using hand-crafted HTML anchor tags.
The generated GroovyDoc HTML looks pretty clean. Building a tag file from it shouldn't be too hard. I'll only implement that if / when I need to.
Groovy's -n command line option is used to read a file line by line. I wrongly assumed that -n implied -e.
e.g. I tried this:
This fails with a "file not found" exception, as it thinks everything after the -n is the path to a Groovy source file.
The correct command will use both -n and e, like this:
When a code block is in a language that Doxygen doesn't recognise, or regards as text, \ characters are treated as the start of an escape sequence.
Find me coding on GitHub, networking on LinkedIn, answering questions on Stack Exchange and hanging out on twitter.