Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 17197 invoked from network); 19 Mar 2010 20:54:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Mar 2010 20:54:49 -0000 Received: (qmail 99687 invoked by uid 500); 19 Mar 2010 20:54:48 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 99656 invoked by uid 500); 19 Mar 2010 20:54:48 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 99648 invoked by uid 99); 19 Mar 2010 20:54:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Mar 2010 20:54:48 +0000 X-ASF-Spam-Status: No, hits=-1073.5 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Mar 2010 20:54:47 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8E8C7234C4AF for ; Fri, 19 Mar 2010 20:54:27 +0000 (UTC) Message-ID: <214919747.373581269032067582.JavaMail.jira@brutus.apache.org> Date: Fri, 19 Mar 2010 20:54:27 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-6635) Install or deploy source jars to maven repo In-Reply-To: <1995629254.314101268836107275.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847573#action_12847573 ] Hadoop QA commented on HADOOP-6635: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12439301/HADOOP-6635.patch against trunk revision 923619. +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 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/424/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/424/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/424/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/424/console This message is automatically generated. > Install or deploy source jars to maven repo > ------------------------------------------- > > Key: HADOOP-6635 > URL: https://issues.apache.org/jira/browse/HADOOP-6635 > Project: Hadoop Common > Issue Type: Improvement > Components: build > Reporter: Patrick Angeles > Fix For: 0.22.0 > > Attachments: HADOOP-6635-branch-20.patch, HADOOP-6635.patch > > > Publishing source jars to the local m2 cache or a public maven repo is extremely handy for Hadoop users that want to be able to inspect the Hadoop source from within their IDE. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.