Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <797905846.1256160059547.JavaMail.jira@brutus>
Date: Wed, 21 Oct 2009 21:20:59 +0000 (UTC)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6326) Hundson runs should check for
 AspectJ warnings and report failure if any is present
In-Reply-To: <1773984231.1256159590166.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik commented on HADOOP-6326:
--------------------------------------------

Most of AspectJ advises are located within HDFS code at the moment. We are seeing a significant number of such issues during an active code development (see HDFS-722 or HDFS-597).

> Hundson runs should check for AspectJ warnings and report failure if any is present
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-6326
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6326
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Konstantin Boudnik
>            Priority: Critical
>
> When a code modifications break AspectJ bindings the following warning appears in the ant's build output:
> {noformat}
>      [echo] Start weaving aspects in place
>      [iajc] warning at /Users/cos/work/branch-0.21/src/test/aop/org/apache/hadoop/hdfs/server/datanode/FSDatasetAspects.aj:55::0 advice defined in org.apache.hadoop.hdfs.server.datanode.FSDatasetAspects has not been applied [Xlint:adviceDidNotMatch]
>      [echo] Weaving of aspects is finished
> {noformat}
> Build process (in particular under Hudson) needs to check the output for such warnings and fail the build if any is present

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.