Is this conversation spanning two lists? I would think the ActiveMQ community (those that aren't camel riders) would want to be involved, too. This should probably move to the ActiveMQ dev list.
On Tue, Sep 18, 2012 at 8:18 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > 1) > I have experimented a bit and so far the best tradeoff I have is > > lib > lib/camel > lib/optional > lib/web > lib/extra > > I moved the camel JARs into a separate lib, as Camel can be made > optional (only web requires it). > In lib/optional I have all the optional stuff, except for mqtt and leveldb. > mqtt and leveldb are in lib/extra. They have a few shared JARs which > is the hawt stuff. > > > 2) > I am considering having all the mandatory in a lib/core instead of the > root of lib. Then its very clean. > Then it becomes: > lib/core > lib/camel > lib/optional > lib/web > lib/extra > > Any thoughts? > > > > > On Mon, Sep 17, 2012 at 5:18 PM, Gary Tully <gary.tu...@gmail.com> wrote: >> +1 to segregate a bit >> >> maybe any common jar goes into optional (to avoid dups) >> >> so for mqtt two dirs are needed, optional and optional/mqtt >> >> /lib/optiona >> /lib/optional/mqtt >> >> etc >> >> On 17 September 2012 08:53, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> Hi >>> >>> I was working on >>> https://issues.apache.org/jira/browse/AMQ-4053 >>> >>> In the AMQ distro (eg the zip / tarball) we have a lib directory with >>> the mandatory JARs. >>> And then a number of sub dirs for >>> - optional >>> - web >>> >>> I would like to propose that we introduce a 1 or 2 more sub dirs to >>> better splitup the JARs. This alos allows people to better understand >>> what the zillion JARs in the optional dir is used for. >>> >>> Its most noticeable the leveldb support that brings in a zillion JARs >>> and libraries such as hadoop etc. >>> So I propose to move that into its own directory such as: >>> >>> - optional >>> - extra >>> - web >>> >>> Or >>> - optional >>> - leveldb >>> - mqtt >>> - web >>> >>> For end users who may not want to use leveldb/mqtt, they can zap those >>> dirs and make a smaller AMQ distro. >>> Maybe also if they re-package and make their own distro within their >>> company to be distributed. >>> >>> Also its less confusing for people thinking that AMQ uses Hadoop etc. >>> >>> Any thoughts? >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> FuseSource >>> Email: cib...@fusesource.com >>> Web: http://fusesource.com >>> Twitter: davsclaus, fusenews >>> Blog: http://davsclaus.com >>> Author of Camel in Action: http://www.manning.com/ibsen >> >> >> >> -- >> http://fusesource.com >> http://blog.garytully.com > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen
