Has anyone managed to update the sourceforge maven-doxygen-plugin to
work with version 1.3.9.1? Or even updated it so that it uses a later
version of doxygen?
I downloaded the new ant_doxygen.jar task (1.4) from SF, renamed the
jar to ant-doxygen-1.4,jar, and placed it in my local repository since
it wasn't at ibiblio.
I modified the project.xml to require version 1.4 of the jar in my maven cache.
I added the doxygen properties to my project.properties file.
maven.doxygen.aliases=""
maven.doxygen.mavenize=true
maven.doxygen.allexternals=YES
maven.doxygen.alphaveticalIndex=YES
maven.doxygen.alwaysDetailedSec=NO
maven.doxygen.binAbsPath=/usr/local/bin
maven.doxygen.binaryToc=NO
maven.doxygen.briefMemberDesc=YES
maven.doxygen.caseSenseName=YES
maven.doxygen.cgiName=doxygen
I got an error about a doxgen.css resource being missing, which it
was. I don't know where that was supposed to come from but I made a
fake one using another plugin's css (I'm definitely NOT a visual guy)
Once that error was out of the way, I'm able to generate doxygen docs.
However, there are a couple of issues:
1. What's the maven.doxygen.output property as opposed to
maven.doxygen.outputDirectory? Neither are listed on the docs for the
plugin and they look like they'd produce approximately correct
locations even though I think at least one is redundant.
2. Why does the ant task always produce the doxygen documentation in
${myprojectbasedirectory}/doc rather than in the location that the
jelly script provides (in maven.doxygen.outputDirectory, which is set
to ${maven.docs.dest}/doxygen which is where I'd like them to go?
The ant task specifies the doc directory, but I'm not well-versed at
writing ant tasks so I have no idea how the attributes specified on
the maven jelly task call get transported inside the task. The cheap
answer is that I could always take the ant task and recompile a
special version that puts the docs into my specific location. That
just doesn't seem right to me.
It looks like the ant task matured and now passes all it's properties
in side as nested <property> tags. So it's possible, given that I
don't have the code for the previous ant-task, that I'll have to
completely alter the jelly script to pass all the possible config
items in.
Anyone else have these issues and maybe some alternate suggestions?
Would it be possible to get ver 1.4 of the ant-doxygen task added to ibiblio?
Thanks,
Mykel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
