hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8186) Untether javadoc and site build
Date Sat, 23 Mar 2013 04:29:15 GMT

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

Hudson commented on HBASE-8186:
-------------------------------

Integrated in HBase-TRUNK #3988 (See [https://builds.apache.org/job/HBase-TRUNK/3988/])
    HBASE-8186 Untether javadoc and site build (Revision 1460037)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/dev-support/test-patch.sh
* /hbase/trunk/pom.xml
* /hbase/trunk/src/docbkx/developer.xml

                
> Untether javadoc and site build
> -------------------------------
>
>                 Key: HBASE-8186
>                 URL: https://issues.apache.org/jira/browse/HBASE-8186
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: 81816.txt, 8186.095.txt
>
>
> Currently javadoc is built when site is invoked.  It is tied to the pre-site scope. 
The javadoc goal is aggregate.  Aggregate goals should be run from the command line generally,
not tied to scopes else they tend to trigger package invocations in sub-modules (http://www.sonatype.com/books/mvnref-book/reference/assemblies-sect-basics.html).
> This issue manifests as mvn build failing because we can't find hbase-*.jar dependencies
even though we don't think we want them since we're just doing a site build (We've seen this
on jenkins build where Nick added the site check; up there the workaround was adding a -N
-- do not recurse -- flag).
> Let me remove building javadoc from site lifecycle.  Invoke it explicitly on the command
line if you need it.    Will update the refguide and remove the -N from the dev-tools as part
of this patch.

--
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