Hello again,
Well after getting up to date with Maven and all the problems I have
reached to a solution. I will explain it here because I need your
opinion on this.
The idea is to make a general configuration of the javadoc plugin in
james parent POM, one that will not contain the APIviz doclet part.
This will be done in the pluginManagement section of the POM. This
general configuration will be for all projects that inherit from
parent.
After this, add the APIviz specific part to the javadoc module in
every module that has classes, so that the doclet will be called only
for those, and thus avoid the error.
The downside of this approach is that this cofiguration will have to
be made in every module and just server has 31. Also, the project will
have to be compiled manually before the site generation.
The addition will look like:
<!-- Configure APIviz JavaDoc generation for this module -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<doclet>org.jboss.apiviz.APIviz</doclet>
<docletArtifact>
<groupId>org.jboss.apiviz</groupId>
<artifactId>apiviz</artifactId>
<version>${apiviz.version}</version>
</docletArtifact>
<additionalparam>-sourceclasspath
${project.build.outputDirectory}</additionalparam>
</configuration>
</plugin>
p.s. I wrote to Trustin to see if we can make APIviz fail silently in
case of missing classes.
Bye,
--
Ioan Eugen Stan
http://ieugen.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
