[jira] [Resolved] (HDFS-2031) request HDFS test-patch to support coordinated change in COMMON jar, for post-patch build only

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HDFS-2031.
------------------------------------
    Resolution: Fixed

This has effectively been fixed.

> request HDFS test-patch to support coordinated change in COMMON jar, for post-patch build only
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-2031
>                 URL: https://issues.apache.org/jira/browse/HDFS-2031
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: build
>            Reporter: Matt Foley
>
> For dev test, need to test an HDFS patch that is dependent on a modified COMMON jar.
> For casual testing, one can build in COMMON with "ant mvn-install", then build in HDFS with "ant -Dresolvers=internal", and the modified COMMON jar from the local maven cache (~/.m2/) will be used in the HDFS build.  This works fine.
> However, running test-patch locally should build:
> * pre-patch: build unmodified HDFS with reference to generic Apache COMMON jar (because the modified COMMON jar may be incompatible with the unmodified HDFS)
> * post-patch:  build modified HDFS with reference to custom local COMMON jar
> Currently, each developer has their favorite way to hack build.xml to make this work.  It would be nice if an ant build switch was available for this use case.  It seems to me the easiest way to accomodate it would be to make "-Dresolvers=internal" be effective only for the post-patch build of test-patch, and let the pre-patch build use the generic Apache jar.
> Of course the same thing applies to MAPREDUCE test-patch when dependent on modified COMMON and/or HDFS jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)