ACCUMULO-1405 should address this issue (the commons dependencies should also be implied).
We have been contemplating several different scenarios and trying to find a solution that works out for everyone. Jim, I think it would be useful to capture the expectations for your clojure use-case as well. On Monday, May 27, 2013, Christopher wrote: > 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 <klu...@gmail.com<javascript:;>> > 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. >
