Apologies. It seems I didn't look into the docs as much as I should have. The
trick is to use the maven-javadoc-plugin resourceArtifacts parameter.
I've documented a recipe for how an organization may centralize its Javadoc
branding in this answer on SO:http://stackoverflow.com/a/30668813/1504556
On Friday, May 29, 2015 6:35 AM, Peter Hansson
wrote:
Hi all,
I would like to be able to centralize our company's branding of Javadoc
and cannot figure out how to do that with the Javadoc plugin.
All projects in our company inherit from the same POM, known as our company pom.
So far, so good.
We've managed to centralize the use of our Javadoc *stylesheet* by doing the
following in the company pom:
org.apache.maven.plugins
maven-javadoc-plugin
2.9.1
com/acme/javadoc/jdoc-stylesheet.css
com.acme.javadoc
stylesheet
1.0
jar
This works well and is also quite well documented by the plugin (thanks!).
However a 'branding package' contains other things than just a stylesheet,
namely things such as images (logos), js files, etc. While the javadoc plugin
has indeed several options to let you include resources (the word for images,
etc)
there doesn't seem to be a way to do this via a dependency, meaning there
doesn't
seem to be a way that we can centralize our javadoc 'branding package'.
How do people generally solve this issue?
Peter
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
