hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3532) Create build targets to create api change reports using jdiff
Date Wed, 11 Jun 2008 17:50:45 GMT

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


Mime
View raw message