hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7593) [site] Adjustments to suit our new publishing process
Date Wed, 16 Jan 2013 23:42:12 GMT

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

Nick Dimiduk commented on HBASE-7593:
-------------------------------------

{code}
+      <site>
+          <id>hbase.apache.org</id>
+          <name>HBase Website at hbase.apache.org</name>
+          <url>file:///tmp</url>
+      </site>
{code}

What's with the tmp file path? Shouldn't think be something like 'http://hbase.apache.org'?

{code}
+              # Getting the javadoc into site is a little tricky.  You have to build it independent,
then
+              # 'aggregate' it at top-level so the pre-site site lifecycle step can find
it; that is
+              # what the javadoc:javadoc and javadoc:aggregate is about.
+              $ MAVEN_OPTS=" -Xmx3g" mvn clean -DskipTests javadoc:javadoc javadoc:aggregate
site  site:stage -
{code}

My maven-foo is weak, but I believe there are hooks allowing you to tie execution of one goal
to a lifecycle phase of another. This seems like a good candidate for attaching the {{javadoc:javadoc}}
and {{javadoc:aggregate}} targets to {{site}}. I managed something along these lines with
the assembly plugin in the [HBaseIA/Twitbase pom|https://github.com/hbaseinaction/twitbase/blob/master/pom.xml#L32].
                
> [site] Adjustments to suit our new publishing process
> -----------------------------------------------------
>
>                 Key: HBASE-7593
>                 URL: https://issues.apache.org/jira/browse/HBASE-7593
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: site.txt
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message