The secure RPC engine would still have to be split off into a separate tree, since there are some classes that derive from the SASL support and token authentication in secure Hadoop. Can't break compilation of the non-secure profile. If there's a way to add an extra source tree in a profile, that could work.
My impression of maven was that it's more "regulated" than that, and that modules were the blessed way of doing multiple source trees. But I'll try some experiments. Any additional pointers are appreciated. On Wed, Sep 7, 2011 at 10:40 AM, Stack <[email protected]> wrote: > On Wed, Sep 7, 2011 at 9:26 AM, Gary Helmling <[email protected]> wrote: > > I was going to start a thread on modularizing pre-0.92, but given that's > > there's no actual patch ready, only a JIRA (HBASE-4336), that seems > > premature. We can race and see how long it takes to put something > together, > > then call a vote if it's ready before we've branched. > > > > Could you do build against hadoop security as a profile (witness the > 0.23 and 0.22 profiles)? Then you wouldn't have to move everything > for 0.92... just make sure 0.92 and security work? > St.Ack >
