You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Zurczak (JIRA)" <ji...@apache.org> on 2015/12/15 14:20:46 UTC

[jira] [Commented] (MJAVADOC-410) Get the stylesheet file from an URL

    [ https://issues.apache.org/jira/browse/MJAVADOC-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058039#comment-15058039 ] 

Vincent Zurczak commented on MJAVADOC-410:
------------------------------------------

Hi. It has been a year since I submitted a pull request for this.
I understand Anders' opinion but if the build fails, it can be repaired. My focus (and the one of this issue) is more into the build result. As long as you have the hand on the external resource (web server or whatever), there is no critical risk.

> Get the stylesheet file from an URL
> -----------------------------------
>
>                 Key: MJAVADOC-410
>                 URL: https://issues.apache.org/jira/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.3.4#6332)