[
https://issues.apache.org/jira/browse/HDFS-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan reopened HDFS-830:
------------------------------
I'm going to go ahead and re-open this: we've been using the resolvers:internal
method for a while and, like I had I feared, it's a pain to keep straight which
version is installed and when it is getting called. Also, as noted above,
there was no public discussion on this approach before it was added to the
wiki.
My preference would be a new option, something like,
-Dadditional.jars=<foo.jar>, which would add those jars to the classpath before
the other entries. This would make it easy to automate upstream testing,
building a patched common jar and then passing it to hdfs to be tested against
(and so on for MR). In any case, with some many patches flying around, locally
installing temporary jars is not a good solution.
> change build.xml to look at lib's jars before ivy, to allow overwriting ivy's
> libraries.
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-830
> URL: https://issues.apache.org/jira/browse/HDFS-830
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Attachments: HDFS-830.patch
>
>
> Currently build.xml looks first into ivy's locations ,before picking up jars
> from lib directory.
> We need to change that to allow overwriting ivy's libs with local ones, by
> putting them into lib.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
