hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7864) Building mvn site with Maven < 3.0.2 causes OOM errors
Date Mon, 28 Nov 2011 19:29:41 GMT

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

Hadoop QA commented on HADOOP-7864:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12505373/HADOOP-7864.diff.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/409//console

This message is automatically generated.
                
> Building mvn site with Maven < 3.0.2 causes OOM errors
> ------------------------------------------------------
>
>                 Key: HADOOP-7864
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7864
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.23.0
>         Environment: Maven 3.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>         Attachments: HADOOP-7864.diff.txt, HADOOP-7864.diff.txt
>
>
> If you try to run mvn site with Maven 3.0.0 (and possibly 3.0.1 - haven't actually tested
that), you get hit with unavoidable OOM errors. Switching to Maven 3.0.2 or later fixes this.
The enforcer should require 3.0.2 for builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message