[
https://issues.apache.org/jira/browse/HADOOP-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647357#action_12647357
]
Doug Cutting commented on HADOOP-4605:
--------------------------------------
> the tests need to be Jarred up or something and run under JUnit with the rest
> of the classpath being SVN_HEAD hadoop JARs.
I proposed an alternate, equivalent mechanism: we use an svn tag url in
build.xml to identify the old version, and the current version is defined by
whatever you've checked out. So if you're testing the foo branch and its
build.xml declares back-compatibility with the bar tag, then the
back-compatibility tests would fetch and compile tests from the bar tag. We
don't need to create a jar for either foo's system code or bar's tests. Rather
the ant task that runs these tests uses a classpath with the compiled code for
these on them. Does that make sense?
> should run old version of unit tests to check back-compatibility
> ----------------------------------------------------------------
>
> Key: HADOOP-4605
> URL: https://issues.apache.org/jira/browse/HADOOP-4605
> Project: Hadoop Core
> Issue Type: Improvement
> Components: test
> Reporter: Doug Cutting
>
> We should test back-compatibility by running unit tests from a prior release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
