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 1954C200C75 for ; Sun, 21 May 2017 16:50:54 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 17F1E160BC5; Sun, 21 May 2017 14:50:54 +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 61730160BA4 for ; Sun, 21 May 2017 16:50:53 +0200 (CEST) Received: (qmail 579 invoked by uid 500); 21 May 2017 14:50:52 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 568 invoked by uid 99); 21 May 2017 14:50:52 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 May 2017 14:50:52 +0000 Received: from [192.168.2.189] (unknown [138.207.148.234]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id DAA3F1A031B for ; Sun, 21 May 2017 14:50:51 +0000 (UTC) From: Benedikt Ritter Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry Date: Sun, 21 May 2017 10:50:13 -0400 References: <6405DF56-2169-40A6-A28B-DAE419CE7E41@apache.org> To: Commons Developers List In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) archived-at: Sun, 21 May 2017 14:50:54 -0000 Hello Stephen, > Am 19.05.2017 um 04:52 schrieb Stephen Colebourne = : >=20 > Is reusing ${commons.osgi.symbolicName} a good idea? I thought it is, because this way we will automatically have the = additional entry after we update a component to the new parent pom = version. :o) > It seems to me that each project should have to opt-in to this > attribute, so I'd add a new ${commons.automatic.moduile.name} > variable. I=E2=80=99d go with ${commons.automatic-module-name}. >=20 > One reason is that the attribute should only be added if the project > is suitable for use as a module (eg. no packages that clash with any > other module, doesn't force cycles in dependencies). I'm not convinced > that all commons projects are valid yet. Okay, how do we find out whether a component is valid? >=20 > The second reason is that we will ultimately need to add a real > module-info.java file to each module. The Automatic-Module-Name > attribute is temporary while the commons projects are worked through > and released. When there is a module-info.java file, we definitely > don't want the Automatic-Module-Name attribute (although it does no > harm, it would look bad). >=20 > The opt-in approach is slightly more work, but better in the long run = I think. I=E2=80=99ll try to come up with something when I have the time again. Thank you! Benedikt >=20 > WDYT? > Stephen >=20 >=20 > On 18 May 2017 at 20:21, Gary Gregory wrote: >> On May 18, 2017 12:09 PM, "Benedikt Ritter" = wrote: >>=20 >> Hi, >>=20 >> here is my proposal on how to get the Automatic-Module-Name entry = into our >> MANIFEST files. This change has to be made only in commons parent. = This is >> the change: >>=20 >> Index: pom.xml >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- pom.xml (revision 1795551) >> +++ pom.xml (working copy) >> @@ -601,6 +601,7 @@ >> ${implementation.build}> Implementation-Build> >> = ${maven.compiler.source}> Source-JDK> >> = ${maven.compiler.target}> Target-JDK> >> + ${commons.osgi.symbolicName}> Automatic-Module-Name> >> >> >> >>=20 >>=20 >> For Commons Lang this will create: >>=20 >> Automatic-Module-Name: org.apache.commons.lang3 >>=20 >>=20 >> WDYT? >>=20 >>=20 >> Seems reasonable enough. >>=20 >> Gary >>=20 >> Benedikt >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org