You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Peter Somogyi (JIRA)" <ji...@apache.org> on 2018/12/17 10:37:00 UTC

[jira] [Commented] (HBASE-19177) Determine if custom maven-fluido-skin jar is still necessary

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

Peter Somogyi commented on HBASE-19177:
---------------------------------------

[~elserj] I think this issue is partly solved by moving to com.github.joshelser:maven-fluido-skin. Can we close this one?

> Determine if custom maven-fluido-skin jar is still necessary
> ------------------------------------------------------------
>
>                 Key: HBASE-19177
>                 URL: https://issues.apache.org/jira/browse/HBASE-19177
>             Project: HBase
>          Issue Type: Task
>          Components: website
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: 3.0.0
>
>
> To get a fancy, mobile-friendly website, HBASE-14785 introduced a patched version of the maven-fluido-skin and committed the pre-built jar into our release.
> A few folks have noticed this jar lurking around the 2.0.0 alpha releases. By version number, it doesn't seem like we'd need to have this anymore (and can use the newest version).
> Let's check it out.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)