abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasudeva Nori" <vasun...@gmail.com>
Subject Re: building adapters
Date Tue, 12 Feb 2008 18:15:24 GMT
makes sense to me.

if an adapter requires some external jars (ibatis.jar for ibatis-based
adapter), where do you plan to put those libs?
maybe in adapter/<adapter_name>/lib/ dir?

would be nice to separate the dependent libs for each adapter into its own
dir.


On Feb 12, 2008 10:04 AM, David Calavera <david.calavera@gmail.com> wrote:

> it works for me
>
> On Feb 12, 2008 6:48 PM, James M Snell <jasnell@gmail.com> wrote:
>
> > So far we have JCR, CouchDb and Ibatis based adapters.  These are
> > currently not built as part of the ant or maven build process.  It is
> > likely that we'll get more adapters over time, each with their own sets
> > of dependencies.  With the maven build it is obviously easier to deal
> > with the differences in dependencies.  Things are more difficult in the
> > ant build, however.  While it makes sense to have a complete build that
> > compiles everything, I would rather not require that everyone who wants
> > to build abdera has to download jcr, ibatis, couchdb4j, etc if they
> > don't intend to use those adapters.  I am considering giving each
> > adapter it's own ant build so each can be built independently.  The
> > Abdera distribution build would build each of the adapters but it could
> > be turned off.  The ant files for each of the adapters would be
> > responsible for handling it's own dependencies.  Does that work?
> >
> > - James
> >
>
>
>
> --
> David Calavera
> http://www.thinkincode.net
>

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