hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Somogyi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18320) Address maven-site-plugin upgrade steps
Date Wed, 05 Jul 2017 11:50:00 GMT

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

Peter Somogyi commented on HBASE-18320:
---------------------------------------

I investigated these plugins and the maven-site-plugin upgrade requires significant modification
including site.xml and site.vm change too. I recommend not to upgrade maven-site-plugin now.
Regarding asciidoc I have different opinion. The needed change is minimal, the difference
is pdfmark file generation. In the new version it is not generated by default and pdfmark
extension is used instead of pdfmarks. Do we actually need this file to be generated?

> Address maven-site-plugin upgrade steps
> ---------------------------------------
>
>                 Key: HBASE-18320
>                 URL: https://issues.apache.org/jira/browse/HBASE-18320
>             Project: HBase
>          Issue Type: Bug
>          Components: site
>    Affects Versions: 3.0.0, 2.0.0-alpha-2
>            Reporter: Peter Somogyi
>            Assignee: Peter Somogyi
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18320.master.001.patch
>
>
> HBASE-18264 upgraded maven-site-plugin from 3.4 to 3.5.1 which required some modification.
> The maven-site-plugin version we changed to is inherited from ASF parent pom.
> Upgrade steps: http://maven.apache.org/plugins/maven-site-plugin/migrate.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message