hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19177) Determine if custom maven-fluido-skin jar is still necessary
Date Mon, 06 Nov 2017 16:18:00 GMT

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

Josh Elser commented on HBASE-19177:

bq.  If we can move to a newer/standard maven-fluido-skin probably the maven-site-plugin upgrade
would be simpler.

Good to know. Thanks for sharing your findings, Peter! Will try to dig into this.

> 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: site
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 2.0.0-beta-1
> 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

View raw message