Fine, i understand now. Thanks for your time Jesse. Regards Ram
On Mon, Feb 25, 2013 at 10:18 PM, Jesse Yates <[email protected]>wrote: > Yeah, if you want to use trunk (or 0.95), you need to modify your pom to > add all the hbase modules (-server, -commons, etc). You would have to > modify the pom anyways to bump the version number, so adding a few more > lines for each module shouldnt break the workflow :) > > And yeah, this will affect other projects based on trunk, but they should > have had to make this changes months ago, when we did the modularization > (if they were on trunk then). > > > - Jesse Yates > > Sent from my iPhone. > > On Feb 25, 2013, at 8:24 AM, ramkrishna vasudevan < > [email protected]> wrote: > > > Okie Jesse.. > > So suppose i have an external project that already has a dependency added > > to hbase and the artificat id is 'hbase'. > > > > But i have a need to use the trunk version. So in the external project i > > need to modify the pom as an work around right. That will do. I thought > > this will affect other projects depending on hbase trunk na. > > > > Regards > > Ram > > > > On Mon, Feb 25, 2013 at 9:43 PM, Jesse Yates <[email protected] > >wrote: > > > >> I don't think you need a patch (not sure what Nicholas was commenting on > >> WRT to Elliots work here) - that's the way mutli-module maven projects > work > >> AFAIK. Hopefully, when Elliot does finish the client module though, > pulling > >> in just hbase-client and hbase-common (for client side stuff) will be > >> natural (as opposed to the current where you need all the modules for > the > >> client, including hbase-server). > >> > >> It might be nice though to have a meta artifact that's just > >> hbase-<VERSION>. I did something similar for Phoenix where you basically > >> can build a single jar with all the dependent, compiled sources rolled > into > >> the jar (as opposed to a jar of jars), so we could consider something > like > >> that too. > >> > >> -Jesse > >> ------------------- > >> Jesse Yates > >> @jesse_yates > >> jyates.github.com > >> > >> > >> On Mon, Feb 25, 2013 at 5:37 AM, Nicolas Liochon <[email protected]> > >> wrote: > >> > >>> I understood that Elliot is working on this subject, but I don't know > >>> exactly what he's targeting. Just that it will be ready very soon... > >>> > >>> > >>> > >>> > >>> > >>> On Mon, Feb 25, 2013 at 1:51 PM, ramkrishna vasudevan < > >>> [email protected]> wrote: > >>> > >>>> Thanks N. > >>>> > >>>> So should we change something in the pom.xml for trunk and commit it > as > >>>> part of HBase. If so i will raise a JIRA for the same. > >>>> > >>>> Regards > >>>> Ram > >>>> > >>>> On Mon, Feb 25, 2013 at 4:55 PM, Nicolas Liochon <[email protected]> > >>>> wrote: > >>>> > >>>>> You're just right, Ram :-) > >>>>> > >>>>> > >>>>> On Mon, Feb 25, 2013 at 12:17 PM, ramkrishna vasudevan < > >>>>> [email protected]> wrote: > >>>>> > >>>>>> Hi devs > >>>>>> > >>>>>> I am just learning this maven. So i came across this and not sure > >>>>> whether > >>>>>> am right. > >>>>>> > >>>>>> In the current trunk we say the artificat id as 'hbase'. > >>>>>> > >>>>>> But when we build the 0.95 SNAPSHOT the jar actually falls under > >>>>>> hbase-server. > >>>>>> > >>>>>> So if i have an external project and need to refer to the latest > >>>>> snapshot i > >>>>>> need to make it the artificat id as 'hbase-server' rather than > >>> 'hbase' > >>>> as > >>>>>> how we used to do. > >>>>>> > >>>>>> Changing this will help me pick up the snapshot jar. > >>>>>> > >>>>>> Is what am saying is right? Pls do correct me if am wrong. > >>>>>> > >>>>>> Regards > >>>>>> Ram > >>>>>> > >>>>> > >>>> > >>> > >> >
