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...@codehaus.org> on 2015/01/12 11:12:18 UTC

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

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

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

Hi,

Any news about this?

{quote}If the external source changes, or is removed, your build will change and/or fail.{quote}

If my build fails, I know I will have to fix something.
And in this case, the external resource. That's all. And if for some reason, the URL changed, I will update my build in consequence to point to another URL.

> 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)