maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Hansson <>
Subject Re: Javadoc plugin - centralized branding
Date Fri, 05 Jun 2015 14:38:59 GMT

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: 

     On Friday, May 29, 2015 6:35 AM, Peter Hansson <>


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:


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?


To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message