Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (athena.apache.org: domain of mkienenb@gmail.com designates
 209.85.212.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <46BEA3C8-6888-49EC-826D-D9A64BF615B4@objectstyle.org>
References: <JIRA.12679243.1384447468398@arcas>
 <JIRA.12679243.1384447468398.82457.1384543761671@arcas>
 <F98E9914-96D2-4C99-8EC8-A612660AF819@objectstyle.org>
 <E1B75D4C-7E33-4F3C-8B92-94D538D5C95B@objectstyle.org>
 <CACTXDpv9j+wXLms4VO2S1368q3cdFhbY7LznDdrGNWirpsEUow@mail.gmail.com>
 <58B98B1F-6F44-44B5-B15C-668FAE53E2DE@objectstyle.org>
 <46BEA3C8-6888-49EC-826D-D9A64BF615B4@objectstyle.org>
From: Mike Kienenberger <mkienenb@gmail.com>
Date: Mon, 18 Nov 2013 08:32:27 -0500
Message-ID: 
 <CAM1yOjbSD59yDHJr86GYXnMF7DGuZCGm5FhtBj47XY65RW=uMg@mail.gmail.com>
Subject: Re: back to monolithic cayenne.jar?
To: dev@cayenne.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This one looks good to me..

On Sun, Nov 17, 2013 at 5:05 AM, Andrus Adamchik <andrus@objectstyle.org> w=
rote:
> Now that I gave it some thought, I actually like the idea of a system mod=
ular by default, but including cayenne-all.jar on top of that. It has none =
of the drawbacks of our old =93synthetic=94 cayenne-server and cayenne-clie=
nt. More practically, turns out that cleanly splitting the core and server =
classes is much more effort than I am ready to undertake now. So we ended u=
p with these modules:
>
>  cayenne-di.jar
>  cayenne-server.jar =3D> cayenne-di
>  cayenne-client.jar =3D> cayenne-di, cayenne-server
>
> I guess I=92ll leave it at that until a later time when we can cut smalle=
r modules out of cayenne-server.
>
> Andrus
>
>
> On Nov 17, 2013, at 12:49 AM, Andrus Adamchik <andrus@objectstyle.org> wr=
ote:
>> On Nov 17, 2013, at 12:27 AM, Adrian A. <a.adrian.tech@googlemail.com> w=
rote:
>>
>>>> 1. Monolithic cayenne.jar for regular apps, for ROP clients, for Cayen=
neModeler
>>>> 2. Partial modularity - Client/server split between the modules, with =
separate DI and backend-indepdendent =93core=94 :
>>>> ...
>>>> Anyways, these are our options=85 Feel free to comment, while I contin=
ue my refactoring.
>>> What about offering both? The modules, but also a "cayenne-all.jar"
>>> (or simply "cayenne.jar") ?
>>>
>>>
>>> Adrian
>>
>> This will take us back to aggregation of multiple modules into one. It w=
as not a pretty picture, so now I am *hoping* we can align the source modul=
es with the binaries that we release. However this can be an option for non=
-maven users I guess.
>>
>> A.
>