Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKoQnDUe-Gj2YE0yVZybqr_T+8MOr=nj2S5wesE32Z0aPn7tWQ@mail.gmail.com>
References: 
 <CAKoQnDUe-Gj2YE0yVZybqr_T+8MOr=nj2S5wesE32Z0aPn7tWQ@mail.gmail.com>
Date: Mon, 27 May 2013 21:45:44 -0400
Message-ID: 
 <CAL5zq9aXHnn_c4+VZV09WJ4j2FZTT1eSMJuOvBHPxmEsUUYi2A@mail.gmail.com>
Subject: Re: dependency issue in 1.5... again
From: Christopher <ctubbsii@apache.org>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Mini Accumulo was moved to its own module at the last moment, and
there wasn't time to discuss dependency issues relating to it.

I'm thinking that Mini should not have any "provided" dependencies, so
that depending on it via Maven goes smoothly. However, we still
shouldn't be packaging these dependencies.

An alternative is to make Mini behave the same as regular Accumulo,
and just require you to provide them just as you'd have to if you were
running the real thing.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Mon, May 27, 2013 at 9:13 PM, Jim Klucar <klucar@gmail.com> wrote:
> I know there was a discussion about this earlier, and I'm sorry I missed
> the RC testing window, but I'm still having a problem with miniaccumulo in
> 1.5.
>
> The issue is that in the pom.xml there are dependencies listed as provided.
> (commons-*, zookeeper, hadoop-client, log4j)  This means that when I have a
> dependency on miniaccumulo, I have to also go depend on these other
> libraries. This fact must be learned by reading pom files or launching a
> miniaccumulo and reading the class not found errors in the logs.