On Fri, Nov 11, 2011 at 10:32 AM, Todd Lipcon <[email protected]> wrote: > I agree with Stack - it only changes around dependencies, not code > modules (at this current point in time).
Unfortunately it does bleed through into code as well. At least for hbase test artifact I can NOT run the single one against different versions of Hadoop. I'm less certain about the main artifact, but I believe I also had issues with MR2 there (although it could have been a cascading problem from a test artifact). Anyway, hbase test maven artifact is busted as far as multiple versions of MR are concerned -- that much I know for sure. Personally, I'd say that we have to fix even that. Or at least have a resolution path. May be the answer there is to provide the kind of shims layer -- that would be fine. That's why I asked a question first without suggesting a solution. > Perhaps when you install the artifacts into a repository, though, the > dependencies leak into the dependency list of the installed POM - > meaning that we'd want different POMs installed based on which > dependency should get pulled in. Yup. And that's a second major problem -- dependency leakage. Thanks, Roman.
