[
https://jira.codehaus.org/browse/MJAVADOC-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353125#comment-353125
]
Vincent Zurczak commented on MJAVADOC-410:
------------------------------------------
Well, considering the alternative is not better.
I have 3 Git repositories, each one defining a release group. It means I
release all the Maven modules that are in a source repository. This is because
you can only tag an entire Git repository, unlike SVN (this has pros and cons).
So, I have one repository for my parent.
One for my main project (platform). And one for a related project (tooling).
What I wanted to do is to define common quality rules for my platform and
tooling projects. The overall idea would be to define them in the parent. But
this results in circular dependencies if my parent depends on one of its
children (egg and chicken story). And if I simply make my _build-tools_ module
not a child of the parent, then the *maven-release-plugin* does not release
correctly. So, I would need a fourth Git repository to host my quality project
(CSS stylesheet for the Javadoc, and resources for Checkstyle). Seriously, I
don't like this.
Putting these resources on a web server makes everything simple.
One single parent, that references static resources. I have the control over
this web server. With the *maven-checstyle-plugin*, if the web server is
offline, the build will fail. And with the *maven-javadoc-plugin*, if the web
server is offline, the default CSS will be used (which is totally acceptable
for snapshots, and most unlikely to happen for releases).
I think this kind of feature is really helpful for multi-module projects.
And in particular when they are hosted on Git repositories.
> Get the stylesheet file from an URL
> -----------------------------------
>
> Key: MJAVADOC-410
> URL: https://jira.codehaus.org/browse/MJAVADOC-410
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Affects Versions: 2.10
> Reporter: Vincent Zurczak
> Priority: Minor
>
> Hi,
> When we generate Javadoc with the maven-javadoc-plugin, we can use the
> *stylesheetfile* parameter to specify a custom CSS file for the generated
> HTML pages.
> This file can be a local file, as well as a resource located in Maven
> dependencies. However, it does not work if the parameter value is set to a
> public URL (a static resource on a web server). This would be a nice
> enhancement. Initially, I had created a Maven module that would contain such
> resources, but it resulted in adding a lot of complexity to my release
> process. Having some static resources on a web server is much more simple.
> I wanted to submit a patch myself for this feature.
> But I was wondering how I could do that. This
> [page|http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch]
> indicates we should attach a patch file to this issue. I was wondering if
> proposing pull requests on the GitHub mirror was also working.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
