[
https://issues.apache.org/jira/browse/HADOOP-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560038#action_12560038
]
Doug Cutting commented on HADOOP-2421:
--------------------------------------
> where do i get the "OLD" one ?
The approach I suggested in the Lucene issue was to have some ant properties
that determine the subversion tag url of the prior version. In trunk this
would point to the prior release. We'd update it in trunk after each release
is made. Then the ant build script would check this out in build/ if it didn't
already exist there. We could (and should) permit this to be optimized,
perhaps by permitting folks to override a property so that the prior version is
stored somewhere more permanent than build/, and perhaps use 'svn switch; svn
update' to make sure that the cached prior version contains what we expect.
> Does the user need to download and then pass the path to ant with -D option ?
I'd imagined that specifying -Djdiff.prior.dir would be optional, but would
help performance a lot, but we could make it mandatory, and emit an error if
it's not specified. That might reduce the load on subversion somewhat.
> Release JDiff report of changes between different versions of Hadoop
> --------------------------------------------------------------------
>
> Key: HADOOP-2421
> URL: https://issues.apache.org/jira/browse/HADOOP-2421
> Project: Hadoop
> Issue Type: Improvement
> Components: build
> Reporter: Nigel Daley
> Priority: Minor
>
> Similar to LUCENE-1083, it would be useful to report javadoc differences (ala
> [JDiff|http://www.jdiff.org/]) between Hadoop releases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
