accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Corey Nolet <cjno...@gmail.com>
Subject Re: dependencies within 1.5
Date Mon, 20 May 2013 11:49:01 GMT
I think the ability to run "./bin/accumulo mini" may have introduced this
circular dependency. Perhaps the MiniAccumuloRunner should be moved
somewhere else.
On May 20, 2013 12:07 AM, "Christopher" <ctubbsii@apache.org> wrote:

> What do you mean there isn't a way to know this? Doesn't the server
> POM express the dependency on start, explicitly?
>
> How are you executing MiniAccumuloCluster when you get this error? I'm
> guessing you have a project with a dependency on "accumulo-server"?
>
> Can you elaborate more on this circular dependency risk you mention?
> I'm not sure how "accumulo-server" depending on "accumulo-start" is a
> circular dependency. Are you suggesting "accumulo-start" also has a
> dependency on "accumulo-server"? Because... it shouldn't...
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Sun, May 19, 2013 at 10:10 PM, Jim Klucar <klucar@gmail.com> wrote:
> > MiniAccumuloCluster moved to the 'server' module, which is fine.
> However, I
> > now have to have a dependency on accumulo-start and accumulo-server to be
> > able to use the MiniAccumuloCluster.  There isn't really any way of know
> > that until you fire up a MiniAccumloCluster object and call .start() and
> > get a ClassNotFoundException on the Main class from accumulo-start.
>  Seems
> > like depending on accumulo-server should pull in accumulo-start (creates
> > circular dependency?) or some other solution should be found.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message