Return-Path: X-Original-To: apmail-cayenne-dev-archive@www.apache.org Delivered-To: apmail-cayenne-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7599110B46 for ; Sun, 17 Nov 2013 10:05:56 +0000 (UTC) Received: (qmail 59730 invoked by uid 500); 17 Nov 2013 10:05:56 -0000 Delivered-To: apmail-cayenne-dev-archive@cayenne.apache.org Received: (qmail 59644 invoked by uid 500); 17 Nov 2013 10:05:51 -0000 Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cayenne.apache.org Delivered-To: mailing list dev@cayenne.apache.org Received: (qmail 59636 invoked by uid 99); 17 Nov 2013 10:05:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Nov 2013 10:05:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.78.103.231] (HELO vorsha.objectstyle.org) (208.78.103.231) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 17 Nov 2013 10:05:46 +0000 Received: (qmail 6711 invoked from network); 17 Nov 2013 10:13:56 -0000 Received: from unknown (HELO ?192.168.2.103?) (212.98.191.4) by vorsha.objectstyle.org with SMTP; 17 Nov 2013 10:13:56 -0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: back to monolithic cayenne.jar? From: Andrus Adamchik In-Reply-To: <58B98B1F-6F44-44B5-B15C-668FAE53E2DE@objectstyle.org> Date: Sun, 17 Nov 2013 13:05:23 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <46BEA3C8-6888-49EC-826D-D9A64BF615B4@objectstyle.org> References: <58B98B1F-6F44-44B5-B15C-668FAE53E2DE@objectstyle.org> To: dev@cayenne.apache.org X-Mailer: Apple Mail (2.1822) X-Virus-Checked: Checked by ClamAV on apache.org Now that I gave it some thought, I actually like the idea of a system = modular 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-client. 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 up with these modules: cayenne-di.jar=20 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 = smaller modules out of cayenne-server. Andrus On Nov 17, 2013, at 12:49 AM, Andrus Adamchik = wrote: > On Nov 17, 2013, at 12:27 AM, Adrian A. = wrote: >=20 >>> 1. Monolithic cayenne.jar for regular apps, for ROP clients, for = CayenneModeler >>> 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 = continue my refactoring. >> What about offering both? The modules, but also a "cayenne-all.jar" >> (or simply "cayenne.jar") ? >>=20 >>=20 >> Adrian >=20 > This will take us back to aggregation of multiple modules into one. It = was not a pretty picture, so now I am *hoping* we can align the source = modules with the binaries that we release. However this can be an option = for non-maven users I guess. >=20 > A.