ramkrishna vasudevan
2013-02-25, 11:17
Nicolas Liochon
2013-02-25, 11:25
ramkrishna vasudevan
2013-02-25, 12:51
Nicolas Liochon
2013-02-25, 13:37
Jesse Yates
2013-02-25, 16:13
ramkrishna vasudevan
2013-02-25, 16:24
Jesse Yates
2013-02-25, 16:48
ramkrishna vasudevan
2013-02-25, 16:52
ramkrishna vasudevan
2013-02-25, 17:26
Jesse Yates
2013-02-25, 17:35
Elliott Clark
2013-02-25, 17:36
Jesse Yates
2013-02-25, 17:39
Andrew Purtell
2013-02-25, 17:49
Stack
2013-02-25, 20:04
Andrew Purtell
2013-02-25, 23:29
ramkrishna vasudevan
2013-02-26, 02:49
-
Artifact id for HBase - trunkramkrishna vasudevan 2013-02-25, 11:17
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
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
+
ramkrishna vasudevan 2013-02-25, 11:17
-
Re: Artifact id for HBase - trunkNicolas Liochon 2013-02-25, 11:25
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
>
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
>
+
Nicolas Liochon 2013-02-25, 11:25
-
Re: Artifact id for HBase - trunkramkrishna vasudevan 2013-02-25, 12:51
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
> >
>
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
> >
>
+
ramkrishna vasudevan 2013-02-25, 12:51
-
Re: Artifact id for HBase - trunkNicolas Liochon 2013-02-25, 13:37
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
> > >
> >
>
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
> > >
> >
>
+
Nicolas Liochon 2013-02-25, 13:37
-
Re: Artifact id for HBase - trunkJesse Yates 2013-02-25, 16:13
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
> > > >
> > >
> >
>
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
> > > >
> > >
> >
>
+
Jesse Yates 2013-02-25, 16:13
-
Re: Artifact id for HBase - trunkramkrishna vasudevan 2013-02-25, 16:24
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
> > > > >
> > > >
> > >
> >
>
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
> > > > >
> > > >
> > >
> >
>
+
ramkrishna vasudevan 2013-02-25, 16:24
-
Re: Artifact id for HBase - trunkJesse Yates 2013-02-25, 16:48
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
>>>>>>
>>>>>
>>>>
>>>
>>
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
>>>>>>
>>>>>
>>>>
>>>
>>
+
Jesse Yates 2013-02-25, 16:48
-
Re: Artifact id for HBase - trunkramkrishna vasudevan 2013-02-25, 16:52
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
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
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
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
+
ramkrishna vasudevan 2013-02-25, 16:52
-
Re: Artifact id for HBase - trunkramkrishna vasudevan 2013-02-25, 17:26
Had more doubt
In the hbase-server-0.95-SNAPSHOT.pom we specify
<parent>
<artifactId>hbase</artifactId>
<groupId>org.apache.hbase</groupId>
<version>0.95-SNAPSHOT</version>
So here also the artificat id is hbase. Is this right? Some one will try
to use the pom attached with that module right and try writing his
project's pom.
Just asking these questions to learn. I may be wrong here.
Regards
Ram
On Mon, Feb 25, 2013 at 10:22 PM, ramkrishna vasudevan <
[EMAIL PROTECTED]> wrote:
> 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
In the hbase-server-0.95-SNAPSHOT.pom we specify
<parent>
<artifactId>hbase</artifactId>
<groupId>org.apache.hbase</groupId>
<version>0.95-SNAPSHOT</version>
So here also the artificat id is hbase. Is this right? Some one will try
to use the pom attached with that module right and try writing his
project's pom.
Just asking these questions to learn. I may be wrong here.
Regards
Ram
On Mon, Feb 25, 2013 at 10:22 PM, ramkrishna vasudevan <
[EMAIL PROTECTED]> wrote:
> 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
+
ramkrishna vasudevan 2013-02-25, 17:26
-
Re: Artifact id for HBase - trunkJesse Yates 2013-02-25, 17:35
No worries Ram!
In this case, yes the artifactID is indeed 'hbase', but because it is a
parent module it doesn't make an actual artifact. From the sonatype maven
book:
The parent project doesn’t create a JAR or a WAR like our previous
> projects; instead, it is simply a POM that refers to other Maven projects.
> The appropriate packaging for a project like simple-parent that simply
> provides a Project Object Model is pom.
-
http://www.sonatype.com/books/mvnex-book/reference/multimodule-sect-simple-parent.html
So another project could reference it, but it really wouldn't do anything
for that project because there is no code content in that dependency.
-Jesse
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 25, 2013 at 9:26 AM, ramkrishna vasudevan <
[EMAIL PROTECTED]> wrote:
> Had more doubt
> In the hbase-server-0.95-SNAPSHOT.pom we specify
>
> <parent>
> <artifactId>hbase</artifactId>
> <groupId>org.apache.hbase</groupId>
> <version>0.95-SNAPSHOT</version>
>
> So here also the artificat id is hbase. Is this right? Some one will try
> to use the pom attached with that module right and try writing his
> project's pom.
> Just asking these questions to learn. I may be wrong here.
>
> Regards
> Ram
>
> On Mon, Feb 25, 2013 at 10:22 PM, ramkrishna vasudevan <
> [EMAIL PROTECTED]> wrote:
>
> > 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...
In this case, yes the artifactID is indeed 'hbase', but because it is a
parent module it doesn't make an actual artifact. From the sonatype maven
book:
The parent project doesn’t create a JAR or a WAR like our previous
> projects; instead, it is simply a POM that refers to other Maven projects.
> The appropriate packaging for a project like simple-parent that simply
> provides a Project Object Model is pom.
-
http://www.sonatype.com/books/mvnex-book/reference/multimodule-sect-simple-parent.html
So another project could reference it, but it really wouldn't do anything
for that project because there is no code content in that dependency.
-Jesse
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 25, 2013 at 9:26 AM, ramkrishna vasudevan <
[EMAIL PROTECTED]> wrote:
> Had more doubt
> In the hbase-server-0.95-SNAPSHOT.pom we specify
>
> <parent>
> <artifactId>hbase</artifactId>
> <groupId>org.apache.hbase</groupId>
> <version>0.95-SNAPSHOT</version>
>
> So here also the artificat id is hbase. Is this right? Some one will try
> to use the pom attached with that module right and try writing his
> project's pom.
> Just asking these questions to learn. I may be wrong here.
>
> Regards
> Ram
>
> On Mon, Feb 25, 2013 at 10:22 PM, ramkrishna vasudevan <
> [EMAIL PROTECTED]> wrote:
>
> > 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...
+
Jesse Yates 2013-02-25, 17:35
-
Re: Artifact id for HBase - trunkElliott Clark 2013-02-25, 17:36
On Mon, Feb 25, 2013 at 9:26 AM, ramkrishna vasudevan <
[EMAIL PROTECTED]> wrote:
> So here also the artificat id is hbase. Is this right? Some one will try
> to use the pom attached with that module right and try writing his
> project's pom.
>
That's saying that this is a module and that this module is a child of the
"hbase" artifact.
In hbase-server the actual artifactid is set on line 29
<https://github.com/apache/hbase/blob/trunk/hbase-server/pom.xml#L29>
(currently).
[EMAIL PROTECTED]> wrote:
> So here also the artificat id is hbase. Is this right? Some one will try
> to use the pom attached with that module right and try writing his
> project's pom.
>
That's saying that this is a module and that this module is a child of the
"hbase" artifact.
In hbase-server the actual artifactid is set on line 29
<https://github.com/apache/hbase/blob/trunk/hbase-server/pom.xml#L29>
(currently).
+
Elliott Clark 2013-02-25, 17:36
-
Re: Artifact id for HBase - trunkJesse Yates 2013-02-25, 17:39
+1 on Elliot's explaination - much better.
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 25, 2013 at 9:36 AM, Elliott Clark <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2013 at 9:26 AM, ramkrishna vasudevan <
> [EMAIL PROTECTED]> wrote:
>
> > So here also the artificat id is hbase. Is this right? Some one will
> try
> > to use the pom attached with that module right and try writing his
> > project's pom.
> >
>
> That's saying that this is a module and that this module is a child of the
> "hbase" artifact.
>
> In hbase-server the actual artifactid is set on line 29
> <https://github.com/apache/hbase/blob/trunk/hbase-server/pom.xml#L29>
> (currently).
>
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Feb 25, 2013 at 9:36 AM, Elliott Clark <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2013 at 9:26 AM, ramkrishna vasudevan <
> [EMAIL PROTECTED]> wrote:
>
> > So here also the artificat id is hbase. Is this right? Some one will
> try
> > to use the pom attached with that module right and try writing his
> > project's pom.
> >
>
> That's saying that this is a module and that this module is a child of the
> "hbase" artifact.
>
> In hbase-server the actual artifactid is set on line 29
> <https://github.com/apache/hbase/blob/trunk/hbase-server/pom.xml#L29>
> (currently).
>
+
Jesse Yates 2013-02-25, 17:39
-
Re: Artifact id for HBase - trunkAndrew Purtell 2013-02-25, 17:49
Might be nice to have an assembly target that produces an uber jar.
On Mon, Feb 25, 2013 at 8:13 AM, 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
> > > > >
> > > >
> > >
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
On Mon, Feb 25, 2013 at 8:13 AM, 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
> > > > >
> > > >
> > >
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
+
Andrew Purtell 2013-02-25, 17:49
-
Re: Artifact id for HBase - trunkStack 2013-02-25, 20:04
On Mon, Feb 25, 2013 at 9:49 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> Might be nice to have an assembly target that produces an uber jar.
>
>
But you'll need a D9 [1] to move it after it's built.
St.Ack
1. http://en.wikipedia.org/wiki/Caterpillar_D9
> Might be nice to have an assembly target that produces an uber jar.
>
>
But you'll need a D9 [1] to move it after it's built.
St.Ack
1. http://en.wikipedia.org/wiki/Caterpillar_D9
+
Stack 2013-02-25, 20:04
-
Re: Artifact id for HBase - trunkAndrew Purtell 2013-02-25, 23:29
LOL
On Mon, Feb 25, 2013 at 12:04 PM, Stack <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2013 at 9:49 AM, Andrew Purtell <[EMAIL PROTECTED]>
> wrote:
>
> > Might be nice to have an assembly target that produces an uber jar.
> >
> >
> But you'll need a D9 [1] to move it after it's built.
> St.Ack
>
> 1. http://en.wikipedia.org/wiki/Caterpillar_D9
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
On Mon, Feb 25, 2013 at 12:04 PM, Stack <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2013 at 9:49 AM, Andrew Purtell <[EMAIL PROTECTED]>
> wrote:
>
> > Might be nice to have an assembly target that produces an uber jar.
> >
> >
> But you'll need a D9 [1] to move it after it's built.
> St.Ack
>
> 1. http://en.wikipedia.org/wiki/Caterpillar_D9
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
+
Andrew Purtell 2013-02-25, 23:29
-
Re: Artifact id for HBase - trunkramkrishna vasudevan 2013-02-26, 02:49
Thanks to all for explaining in understanding this.
Thanks to Jesse and Elliot in particular.
Regards
Ram
On Tue, Feb 26, 2013 at 4:59 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> LOL
>
>
> On Mon, Feb 25, 2013 at 12:04 PM, Stack <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Feb 25, 2013 at 9:49 AM, Andrew Purtell <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Might be nice to have an assembly target that produces an uber jar.
> > >
> > >
> > But you'll need a D9 [1] to move it after it's built.
> > St.Ack
> >
> > 1. http://en.wikipedia.org/wiki/Caterpillar_D9
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Thanks to Jesse and Elliot in particular.
Regards
Ram
On Tue, Feb 26, 2013 at 4:59 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> LOL
>
>
> On Mon, Feb 25, 2013 at 12:04 PM, Stack <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Feb 25, 2013 at 9:49 AM, Andrew Purtell <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Might be nice to have an assembly target that produces an uber jar.
> > >
> > >
> > But you'll need a D9 [1] to move it after it's built.
> > St.Ack
> >
> > 1. http://en.wikipedia.org/wiki/Caterpillar_D9
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
+
ramkrishna vasudevan 2013-02-26, 02:49
