Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo, mail # dev - dependencies within 1.5


Copy link to this message
-
Re: dependencies within 1.5
Christopher 2013-05-21, 18:08
Seems fine to me as well.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, May 21, 2013 at 1:35 PM, John Vines <[EMAIL PROTECTED]> wrote:
> Sounds good to me
>
>
> On Tue, May 21, 2013 at 1:30 PM, Corey Nolet <[EMAIL PROTECTED]> wrote:
>
>> Hadoop's module is "hadoop-minicluster" so I'm thinking of making
>> "accumulo-minicluster". I'm also thinking the package should be
>> "o.a.a.minicluster" Any objections?
>>
>>
>> On Tue, May 21, 2013 at 12:50 PM, Christopher <[EMAIL PROTECTED]> wrote:
>>
>> > +1 for moving it in 1.5 for all the previous reasons specified.
>> >
>> > --
>> > Christopher L Tubbs II
>> > http://gravatar.com/ctubbsii
>> >
>> >
>> > On Tue, May 21, 2013 at 12:36 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>> > > On Tue, May 21, 2013 at 12:34 PM, John Vines <[EMAIL PROTECTED]> wrote:
>> > >
>> > >> I think we should move it in 1.5. The bug Eric found this morning,
>> along
>> > >>
>> > >
>> > > Thats ok w/ me.  I mostly want to avoid the deprecation route.
>> > >
>> > >
>> > >
>> > >> with the laundry list of non-breakers, are enough for an RC5 to be
>> cut.
>> > >> This should be pulled in. Having packages not align with modules
>> causes
>> > >> nothing must frustration and confusion when trying to debug things.
>> > >>
>> > >>
>> > >> On Tue, May 21, 2013 at 12:27 PM, Keith Turner <[EMAIL PROTECTED]>
>> > wrote:
>> > >>
>> > >> > On Tue, May 21, 2013 at 12:16 PM, Corey Nolet <[EMAIL PROTECTED]>
>> > wrote:
>> > >> >
>> > >> > > I think it's worth asking because a few people expressed interest
>> in
>> > >> > moving
>> > >> > > the mini cluster to it's own module. Do we want this for 1.5 or do
>> > we
>> > >> > wait
>> > >> > > until 1.6 and provide a deprecation strategy?
>> > >> > >
>> > >> >
>> > >> > I think we should move it in 1.5 XOR leave the package name the same
>> > in
>> > >> > 1.6, but move it to another module.  Either way avoids API changes
>> for
>> > >> > users.
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> > >
>> > >> > >
>> > >> > > On Mon, May 20, 2013 at 2:10 PM, Corey Nolet <[EMAIL PROTECTED]>
>> > >> wrote:
>> > >> > >
>> > >> > > > Agreed, they also slow down the build.
>> > >> > > >
>> > >> > > >
>> > >> > > > On Mon, May 20, 2013 at 2:09 PM, Christopher <
>> [EMAIL PROTECTED]
>> > >
>> > >> > > wrote:
>> > >> > > >
>> > >> > > >> Maybe...  or 'jar-with-dependencies' assembly, or something
>> > similar,
>> > >> > > >> might be useful.
>> > >> > > >> I'd probably argue for it to be in a de-activated profile, by
>> > >> default,
>> > >> > > >> though. Shaded jars can become problematic if people start
>> using
>> > >> them
>> > >> > > >> as dependencies.
>> > >> > > >>
>> > >> > > >> --
>> > >> > > >> Christopher L Tubbs II
>> > >> > > >> http://gravatar.com/ctubbsii
>> > >> > > >>
>> > >> > > >>
>> > >> > > >> On Mon, May 20, 2013 at 2:00 PM, Corey Nolet <
>> [EMAIL PROTECTED]>
>> > >> > wrote:
>> > >> > > >> > This may be far out into space- but how would you guys feel
>> > about
>> > >> > > >> providing
>> > >> > > >> > a shaded jar in the pom for a new mini module? This may make
>> it
>> > >> > easier
>> > >> > > >> for
>> > >> > > >> > users to run the mini accumulo cluster without
>> hadoop/zookeeper
>> > >> > > >> installed.
>> > >> > > >> >
>> > >> > > >> >
>> > >> > > >> > On Mon, May 20, 2013 at 1:56 PM, Christopher <
>> > [EMAIL PROTECTED]
>> > >> >
>> > >> > > >> wrote:
>> > >> > > >> >
>> > >> > > >> >> ACCUMULO-1436 for fixing "provided" dependencies.
>> > >> > > >> >>
>> > >> > > >> >> --
>> > >> > > >> >> Christopher L Tubbs II
>> > >> > > >> >> http://gravatar.com/ctubbsii
>> > >> > > >> >>
>> > >> > > >> >>
>> > >> > > >> >> On Mon, May 20, 2013 at 12:52 PM, Christopher <
>> > >> [EMAIL PROTECTED]
>> > >> > >
>> > >> > > >> wrote:
>> > >> > > >> >> > You're right. I'm not sure why our internal dependencies
>> > would
>> > >> be
>> > >> > > >> >> > marked as provided... except maybe I made that mistake to
>> > try
>> > >> to
>> > >> > > deal