[
https://issues.apache.org/jira/browse/HBASE-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292759#comment-14292759
]
Andrew Purtell edited comment on HBASE-12918 at 1/27/15 1:04 AM:
-----------------------------------------------------------------
I reviewed the POM changes and earlier branch-1.0 history, the checkstyle
problem pre-exists on branch-1 and master. I think the path to checkstyle.xml
must be fully specified from the project root. It doesn't block 0.98 builds
with site generation, so I'm going to proceed with looking at incorporating the
theme changes. We might need to do more for branch-1, and I wonder if it's an
issue on master.
was (Author: apurtell):
I reviewed the POM changes and earlier branch-1.0 history, the checkstyle
problem pre-exists on branch-1 and master. I think the path to checkstyle.html
must be fully specified from the project root. It doesn't block 0.98 builds
with site generation, so I'm going to proceed with looking at incorporating the
theme changes. We might need to do more for branch-1, and I wonder if it's an
issue on master.
> Backport asciidoc changes
> -------------------------
>
> Key: HBASE-12918
> URL: https://issues.apache.org/jira/browse/HBASE-12918
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Labels: beginner
> Fix For: 1.0.0, 0.98.10, 1.1.0
>
> Attachments: HBASE-12918-0.98.patch.gz, HBASE-12918-0.98.patch.gz,
> HBASE-12918-1.0.patch.gz, HBASE-12918-1.0.patch.gz
>
>
> For releases, we usually whole-sale copy the docs from master to the release
> branch, and do the release with the latest-in-time documentation.
> With the asciidoc change, we cannot do that anymore unless we also get the
> pom.xml changes, etc.
> [~misty] FYI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
