Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <447923076.1213206645124.JavaMail.jira@brutus>
Date: Wed, 11 Jun 2008 10:50:45 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3532) Create build targets to create api
 change reports using jdiff
In-Reply-To: <294739667.1213200525026.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-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604285#action_12604285 ] 

Doug Cutting commented on HADOOP-3532:
--------------------------------------

> Hadoop_${version}.xml

Perhaps use "hadoop-${version}" to better match jar and release names?

The updates to http://wiki.apache.org/hadoop/HowToRelease might also be drafted in this issue.  My guess is that, after the release vote has passed, the release master should generate a new version of this file, from the new release, and commit it to the release branch, to trunk, and to any higher-numbered release branches.  Does that sound right?


> Create build targets to create api change reports using jdiff
> -------------------------------------------------------------
>
>                 Key: HADOOP-3532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3532
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: build
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.18.0
>
>
> I'd like to add support for jdiff to our build scripts, to enable generating api difference reports between versions.

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