Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C1B91200BE1 for ; Mon, 5 Dec 2016 00:36:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BD216160B25; Sun, 4 Dec 2016 23:36:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8FE2A160B0E for ; Mon, 5 Dec 2016 00:36:31 +0100 (CET) Received: (qmail 40982 invoked by uid 500); 4 Dec 2016 23:36:30 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 40972 invoked by uid 99); 4 Dec 2016 23:36:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Dec 2016 23:36:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 31741180335 for ; Sun, 4 Dec 2016 23:36:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=2, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id GrBxrWW73Wna for ; Sun, 4 Dec 2016 23:36:28 +0000 (UTC) Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com [209.85.192.173]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id AAA325F36D for ; Sun, 4 Dec 2016 23:36:27 +0000 (UTC) Received: by mail-pf0-f173.google.com with SMTP id c4so59746897pfb.1 for ; Sun, 04 Dec 2016 15:36:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=Pv7NiHRvMneVA4GpfKNEBMDjrhMdmkG65zoTxpEZlAg=; b=ylJWs+f4kpdOUC5K73tSfQMJL5cZhC8/HqBTZQNU4J6RBrdG84+4MAzNTVUFz0YxsG mE4Eov6PsJJwyFpZXvf3JeerLp8EIW729JzoQKEEA95ooGXj+5G53Q6iT/kSykCQfsy8 Zcs8RExO78ZtMk9lH9i/vgmkxPhgU6ucCWWWmAuJOBPgKZLLXlfvFTkeWADCm/TSSRVZ Er3YLVp5E68RBnjxrSca9M0aRl+4V3nKDcOatnuLmeb2oxiB7tgepC1ShaBfS0878tlI wRy25419md+WHVxXQidfvBfewznNX9UEdOZr3zzO/SBjBReubvCbWL8XWIiMOmJBf4v0 E3cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=Pv7NiHRvMneVA4GpfKNEBMDjrhMdmkG65zoTxpEZlAg=; b=DQYeOZ4qXlyKM3RHSazZU9uwa3DEWBwBAgZ9d9VuGmgS0+yWaqR7mADpppHv32D3Wi EcBQHh+XoyJPXNgAlXCKrMp+t9HY5sWCT0FWtvTdFXHH3b6pqkFywUjFdn6cMmcdVopA WHf/iu7pPYAAPIOXAbTsBU5DEXF/CB1xdH5cZKb6OmpZbn7jG2t62wSdsAckmh+sW+YK uU3yDT4xPjjRNf13MY4qUuWrQ0uuDTe4VYn9xr1QKdZIC8/rrw3xc/0uQ3MAC4xWdf8y FOyVss2hPqqf2stzx33Lsu67qQj6htFZ+8sGMcIQ5gAkW8NGYe81e45Lq/zFG0RZtQic ePVw== X-Gm-Message-State: AKaTC03EMFk9GDbNAth4zd8hZvWMoKQrX6qTzQr4KhI332r1T+Mxsj5eJq0S4oGW4/gOoA== X-Received: by 10.99.131.67 with SMTP id h64mr96306990pge.135.1480894580631; Sun, 04 Dec 2016 15:36:20 -0800 (PST) Received: from [10.32.69.166] (pw126247065022.14.panda-world.ne.jp. [126.247.65.22]) by smtp.gmail.com with ESMTPSA id y200sm22390702pfb.16.2016.12.04.15.36.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Dec 2016 15:36:19 -0800 (PST) From: Remko Popma Content-Type: multipart/alternative; boundary=Apple-Mail-F79CA59E-F405-4FE9-9C3E-23B217E162E4 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Mon, 5 Dec 2016 08:36:13 +0900 Subject: Re: Modules for SQL and MOM/JMS Message-Id: <71BD219C-17A9-4B4B-AB22-67432CD8F817@gmail.com> References: <15456DA4-16A3-48E6-B1B1-67E618917074@dslextreme.com> In-Reply-To: <15456DA4-16A3-48E6-B1B1-67E618917074@dslextreme.com> To: Log4J Developers List X-Mailer: iPhone Mail (14B100) archived-at: Sun, 04 Dec 2016 23:36:32 -0000 --Apple-Mail-F79CA59E-F405-4FE9-9C3E-23B217E162E4 Content-Type: text/plain; charset=shift_jis Content-Transfer-Encoding: quoted-printable I worry that breaking the site up into multiple sub sites is going to make t= he user experience worse. It may make it difficult for users to find things.= =20 And I'm still not convinced that this will speed up the build.... Sent from my iPhone > On 5 Dec 2016, at 7:30, Apache wrote: >=20 > I don=81ft think each of those should be in a separate repository, but it w= ould make sense to have a single repo with all of them as sub projects. >=20 > We do need to determine how we are going to change the layout of the Log4j= site to accommodate all of this as each repository will have its own Maven g= enerated site. I would think we might want to have links to them from the Lo= g4j site that open the referenced site in a new tab? >=20 > Ralph >=20 >> On Dec 4, 2016, at 2:40 PM, Gary Gregory wrote: >>=20 >> OK, I have a log4j-sql module split out locally. But it seems we need ins= tead: >>=20 >> - log4j-db (commons code, depends log4j-core) >> - log4j-jdbc (JDBC only, depends on log4j-db) >> - log4j-jpa (JPA only, depends on log4j-db) >>=20 >> I would also repackage these out of .core. >>=20 >> Thoughts? >>=20 >> Gary >>=20 >>> On Sun, Dec 4, 2016 at 1:28 PM, Gary Gregory wr= ote: >>> Note the common code in .core.db for .core.db.jdbc and .core.db.jpa. It s= eems just that little bit should go in its own module or stay in core. >>>=20 >>> Gary >>>=20 >>>> On Sun, Dec 4, 2016 at 1:15 PM, Gary Gregory w= rote: >>>> Also: package names, it does not make sense to have JDBC and JPA code u= nder the .core. package anymore. I would: >>>>=20 >>>> Create the new modules with code not in .core. and deprecate the equiva= lent in .core. >>>>=20 >>>> Gary >>>>=20 >>>>> On Sun, Dec 4, 2016 at 1:08 PM, Gary Gregory w= rote: >>>>> Hm... this is also an opportunity to pick more precise names: log4j-jd= bc and log4j-jpa >>>>>=20 >>>>> Gary >>>>>=20 >>>>>> On Sun, Dec 4, 2016 at 12:56 PM, Matt Sicker wrote= : >>>>>> As for SQL, the JDBC one doesn't have any dependencies, so that could= stay in core if desired, but the JPA one does require additional Java EE AP= Is, so that'd make sense to separate at the very least. >>>>>>=20 >>>>>> As for the nosql ones, again, it would be nice to split those up so t= hat there aren't optional dependencies. That would either mean a mongo and c= ouch component, or it could also mean an additional nosql-common component (= unless the abstract classes were put into log4j-core). >>>>>>=20 >>>>>>> On 4 December 2016 at 12:44, Gary Gregory w= rote: >>>>>>> Thoughts on splitting out SQL and MOM (JMS) into their own modules? W= e already have a nosql module, having a sql one makes sense. The overall ide= a is to make core lighter. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> --=20 >>>>>> Matt Sicker >>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org=20 >>>>> Java Persistence with Hibernate, Second Edition=20 >>>>> JUnit in Action, Second Edition=20 >>>>> Spring Batch in Action=20 >>>>> Blog: http://garygregory.wordpress.com=20 >>>>> Home: http://garygregory.com/ >>>>> Tweet! http://twitter.com/GaryGregory >>>>=20 >>>>=20 >>>>=20 >>>> --=20 >>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org=20 >>>> Java Persistence with Hibernate, Second Edition=20 >>>> JUnit in Action, Second Edition=20 >>>> Spring Batch in Action=20 >>>> Blog: http://garygregory.wordpress.com=20 >>>> Home: http://garygregory.com/ >>>> Tweet! http://twitter.com/GaryGregory >>>=20 >>>=20 >>>=20 >>> --=20 >>> E-Mail: garydgregory@gmail.com | ggregory@apache.org=20 >>> Java Persistence with Hibernate, Second Edition=20 >>> JUnit in Action, Second Edition=20 >>> Spring Batch in Action=20 >>> Blog: http://garygregory.wordpress.com=20 >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >>=20 >>=20 >>=20 >> --=20 >> E-Mail: garydgregory@gmail.com | ggregory@apache.org=20 >> Java Persistence with Hibernate, Second Edition=20 >> JUnit in Action, Second Edition=20 >> Spring Batch in Action=20 >> Blog: http://garygregory.wordpress.com=20 >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >=20 --Apple-Mail-F79CA59E-F405-4FE9-9C3E-23B217E162E4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I worry that breaking the site up into= multiple sub sites is going to make the user experience worse. It may make i= t difficult for users to find things. 

And I'm still not convinced tha= t this will speed up the build....

Sent from my iPhone

= On 5 Dec 2016, at 7:30, Apache <ralph.goers@dslextreme.com> wrote:

I don=E2=80=99t think each of those should be in a= separate repository, but it would make sense to have a single repo with all= of them as sub projects.

We do need to determine how we are going to change the layout of the= Log4j site to accommodate all of this as each repository will have its own M= aven generated site. I would think we might want to have links to them from t= he Log4j site that open the referenced site in a new tab?

Ralph

On Dec 4, 2016, at 2:40 PM, G= ary Gregory <garydgr= egory@gmail.com> wrote:

=
OK, I have a log4j-sql module sp= lit out locally. But it seems we need instead:

- log4j-db (commons code, depends log4j-core)
- log4j-jdbc (JDBC only, depends on log4j-db)
- log4j-jpa (JPA only, depends on log4j-db)

I would also repackage these out of .core.

Thoughts?

Gary

On Sun, Dec 4, 2016 a= t 1:28 PM, Gary Gregory <garydgregory@gmail.com> wrote:
Note the common code in .core.db for .core.db.jdbc and .core= .db.jpa. It seems just that little bit should go in its own module or stay i= n core.

Gary

=
On Sun, Dec 4, 2016 at 1:15 PM, Gary Gregory <garydgregory@gmail.com> wrote:
Also: packa= ge names, it does not make sense to have JDBC and JPA code under the .core. p= ackage anymore. I would:

Create the new modules with code not in .core. and deprecate the equivalent= in .core.

Gary=

On Sun, Dec 4, 2016 at 1:08 PM, Gary Gregory <garydgregory@gmail.com> wrote:
Hm... this is a= lso an opportunity to pick more precise names: log4j-jdbc and log4j-jpa

Gary

On Sun, Dec 4, 2016 a= t 12:56 PM, Matt Sicker <boards@gmail.com> wrote:
As for SQL, the JDBC one doesn't have any dependencies, so that could sta= y in core if desired, but the JPA one does require additional Java EE APIs, s= o that'd make sense to separate at the very least.

As for the nosql ones, again, it would be nice to s= plit those up so that there aren't optional dependencies. That would either m= ean a mongo and couch component, or it could also mean an additional nosql-c= ommon component (unless the abstract classes were put into log4j-core).

= On 4 December 2016 at 12:44, Gary Gregory <garydgregory@gmail.com> wrote:
=
= Thoughts on splitting out SQL and MOM (JMS) into their own modules? We alrea= dy have a nosql module, having a sql one makes sense. The overall idea is to= make core lighter.



= --
Matt Sicker <boards@gmail.com>



--



--


<= div class=3D"">
--
E-Mail: garydgregory= @gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition 
JUnit in Action, Second Edition 
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! <= a href=3D"http://twitter.com/GaryGregory" target=3D"_blank" class=3D"">http:= //twitter.com/GaryGregory


<= div class=3D"">
--

= --Apple-Mail-F79CA59E-F405-4FE9-9C3E-23B217E162E4--