I agree with Stack - it only changes around dependencies, not code modules (at this current point in time).
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. -Todd On Fri, Nov 11, 2011 at 9:29 AM, Stack <[email protected]> wrote: > On Fri, Nov 11, 2011 at 9:01 AM, Roman Shaposhnik <[email protected]> wrote: >> On Fri, Nov 11, 2011 at 8:45 AM, Stack <[email protected]> wrote: >>> We have maven profilles in our pom for different hadoop versions. >>> This implies build per hadoop version. >> >> Correct. What I'm thinking is that when you build using one of those >> profiles you get bits which are incompatible with a different version >> of Hadoop. As such we need to figure out a way of making these >> artifacts available independently or at least converge on a single >> version of the artifact. >> > > Hmm... I thought it just a packaging issue; what gets assembled as the > product (I could be wrong -- I've not looked at this in a while. > You'd know better Roman). > > St.Ack > -- Todd Lipcon Software Engineer, Cloudera
