From dev-return-165881-archive-asf-public=cust-asf.ponee.io@commons.apache.org Thu Jan 4 15:22:03 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 5AAAC180657 for ; Thu, 4 Jan 2018 15:22:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4A592160C2B; Thu, 4 Jan 2018 14:22:03 +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 6A93D160C28 for ; Thu, 4 Jan 2018 15:22:02 +0100 (CET) Received: (qmail 77711 invoked by uid 500); 4 Jan 2018 14:22:01 -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 77690 invoked by uid 99); 4 Jan 2018 14:22:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2018 14:22:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9EA52C23AF for ; Thu, 4 Jan 2018 14:22:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id VpVX0i_NH9HR for ; Thu, 4 Jan 2018 14:21:59 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 459F15F3D0 for ; Thu, 4 Jan 2018 14:21:59 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id j137so2065172qke.10 for ; Thu, 04 Jan 2018 06:21:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=s9ChR0jl2shJJGXO8jhXi2ez4RjmanBzPd17mC+2lDc=; b=e7FJqYo73EL11Wj18UjML/y0iDlRAf1dpZ036twa/3JDMsZMmu2k6elBeZ7CShRv5+ dtAIIBHfvC82x9hGd6zmjESx9eFKIOjmgO7eKATSJ98uf/1PdvmcVQSHLV3TAPRUTayc GylGjhi7YfrlnjdyCKXPTKK7UGF/YhcJtQQ+Q09lJYMl6nMR7fFNNZmx8MwsWMKsxi7i Xffs6ArqoR4kLjpx+mera7fquxO6EQJd7tP2F9ONem+8IOuvxxpa0YoQ6a9XvmCsBj2w WT8dVGy2YDjwXiRf0hJYaYIvA3YYEnkU2xbRHyZc4O2e5fjphBhQTAHZYCf34C+azvbI gc1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=s9ChR0jl2shJJGXO8jhXi2ez4RjmanBzPd17mC+2lDc=; b=ejfmbsibJsNt/TOrGtVRQhNFRewk/Lds1cRGncFPH4tvpfkIP3kvZkPCsQpy9v913l 2utbRfcSpikXjzYfgS2kS3VSqXcijE8ACfBEi34RdacxF8ZdF0Idv7Ot+CVCjw+6+iVo 3arhmpfXXpPORPgM8LbINtRoc9wuBkD99dNB287EtRt7hCVNnyT84UtTpTqu5CVDU9B9 OYdIbgNaRZVy4/KXkAitVwhGR7r1s2ba5C49tllNx/oIRYy6xwsGFNuXh9c83zYSKEev WfWAlxkzYfhYlL0FWOoNQtI4I2JW30k9iDxn2oCnvzY4IG71LWNhuETfAHbXrWFRCb1U SjeQ== X-Gm-Message-State: AKGB3mKDC9zxJJPkybmcv/5PmM9cQILDT3CXgv9acqHf9MtWRV5KnP/B XqP0G/1lA8XVfjN4alxOoqJNmI57 X-Google-Smtp-Source: ACJfBosbG91KXS6Id3utvpJjEVkzQVmPyJKEZS1TzupEdYhgdRzpVQiBjcfPs2W4J8PvvZ8aO64blw== X-Received: by 10.55.99.140 with SMTP id x134mr6383799qkb.35.1515075713195; Thu, 04 Jan 2018 06:21:53 -0800 (PST) Received: from ?IPv6:2601:5c1:4500:58d0:311d:73b1:e996:a2eb? ([2601:5c1:4500:58d0:311d:73b1:e996:a2eb]) by smtp.gmail.com with ESMTPSA id r85sm2201326qke.32.2018.01.04.06.21.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 06:21:52 -0800 (PST) From: Rob Tompkins Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Thu, 4 Jan 2018 09:21:52 -0500 Subject: Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/) Message-Id: <4C557A35-DE70-4CA8-B0EF-C3CC661A9C34@gmail.com> References: <20180104015947.AD1D03A0168@svn01-us-west.apache.org> <5E0CA10F-8D8C-494F-BF7D-EFCFAE9B7295@gmail.com> <7af282589ebf9dd0e0f867091842fc8d@scarlet.be> <2CCA990F-5611-433B-9888-F6A56079FAEB@gmail.com> <0415812331dd66d49ec9a53a1a6cc845@scarlet.be> <01BDAEBF-8804-4154-AF24-15E5EEC6BC1D@gmail.com> In-Reply-To: To: Commons Developers List X-Mailer: iPhone Mail (15C153) > On Jan 4, 2018, at 9:18 AM, Gilles wrote: >=20 > On Thu, 4 Jan 2018 08:56:09 -0500, Rob Tompkins wrote: >>> On Jan 4, 2018, at 8:41 AM, Gilles wrote:= >>>=20 >>> On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: >>>>> On Jan 4, 2018, at 5:24 AM, Gilles wrot= e: >>>>>=20 >>>>> Hi. >>>>>=20 >>>>>> On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: >>>>>> Hello all, >>>>>>=20 >>>>>> So, now I have a plugin that detaches the distributions, zips the >>>>>> site, and then commits the zipped site, RELEASE-NOTES.txt (from the >>>>>> root), and the distributions to the svn staging area. All from: >>>>>>=20 >>>>>> mvn clean site deploy -Prelease -Duser.name=3Dchtompki >>>>>> -Duser.password=3D >>>>>>=20 >>>>>> Thoughts on pulling this in as a new component and starting to get it= >>>>>> to a more formal state? I=E2=80=99m sure we could add more, but this d= oes take >>>>>> away a considerable portion of the manual steps. >>>>>=20 >>>>> Does it work for modular components? [See below.] >>>>>=20 >>>>>> Also, as I said before I=E2=80=99ve not written any maven unit/integr= ation >>>>>> tests. I do know that I could contrive some unit tests using >>>>>> PowerMockito (but that feels mildly pointless because it is indeed a >>>>>> contrivance with little value). So, I will try to investigate the >>>>>> maven testing mechanics, but what I currently have does indeed work. >>>>>>=20 >>>>>> Should I call a vote for the new component? >>>>>>=20 >>>>>> Cheers, >>>>>> -Rob >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On Jan 3, 2018, at 8:59 PM, chtompki@apache.org wrote: >>>>>>>=20 >>>>>>> Author: chtompki >>>>>>> Date: Thu Jan 4 01:59:44 2018 >>>>>>> New Revision: 24003 >>>>>>>=20 >>>>>>> Log: >>>>>>> Removing commons-text-1.3-SNAPSHOT >>>>>>>=20 >>>>>>> Removed: >>>>>>> dev/commons/text/RELEASE-NOTES.txt >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.tar.gz >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.tar.gz.asc >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.tar.gz.md5 >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.tar.gz.sha1 >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.zip >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.zip.asc >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.zip.md5 >>>>>>> dev/commons/text/binaries/commons-text-1.3-SNAPSHOT-bin.zip.sha1 >>>>>>> dev/commons/text/site.zip >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.tar.gz >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.tar.gz.asc >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.tar.gz.md5 >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.tar.gz.sha1 >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.zip >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.zip.asc >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.zip.md5 >>>>>>> dev/commons/text/source/commons-text-1.3-SNAPSHOT-src.zip.sha1 >>>>>>>=20 >>>>>=20 >>>>> In the case of a modular component, the file >>>>> commons---bin.tar.gz >>>>> should contain the JAR files (codes, sources, javadoc) of all >>>>> the modules, and the file >>>>> commons---src.tar.gz >>>>> should contain the (main) source codes of all the modules. >>>>>=20 >>>>> If your new plugin does that, then it will be unnecessary to >>>>> add an ad-hoc module like "dist-archive" (see e.g. [1]) that >>>>> only exists for the sake of creating those ("include-all") >>>>> "src" and "bin" files. >>>>=20 >>>> Yes. Your have a good point point Gilles. >>>>=20 >>>> It would seem that we would want some flavour of a new distribution >>>> handling mojo for just this case, but I don=E2=80=99t foresee that as b= eing >>>> overly difficult, we=E2=80=99d have to just accommodate for a slightly m= ore >>>> manual process. I still think that with a little work we could make >>>> the signing of those artifacts as well as the upload to svn maven >>>> target based as opposed to you having to copy files around on your >>>> machine and check them in manually. >>>>=20 >>>> Thoughts? >>>=20 >>> Why "more manual process"? Is the modular case any different from the >>> maven API POV (I'd imagine it's "just" building recursively)? >>>=20 >>> Do you plan to add the necessary code as part of your current work on >>> this new plugin? This will surely help for the release of at least >>> RNG >>> Numbers >>> Statistics >>> Math >>> and any other currently (or future) modular component. >>=20 >> I can make it work. It just wasn=E2=80=99t entirely clear to me what comm= and >> you run to build the dists. And, it looks as if you are building dists >> (that aren=E2=80=99t published) for every module in the build. >=20 > [Talking about RNG.] > All modules are published/deployed to Nexus, except "dist-archive" > that only exists to bundle the contents of all the other modules > (separate "bin" and "src", as per Apache requirement). > For that purpose, I had to create a custom POM (in "dist-archive") > to run the "assembly" plugin. Ok yeah, that=E2=80=99s what I was thinking, and I would (after writing the c= ode to do this) have you add another target after =E2=80=9Cassembly:single=E2= =80=9D that would sign and check in the dists to svn. Does that sound approp= riate? >=20 >>=20 >> What is the release process here, and I=E2=80=99ll write something to get= it >> to properly work. >=20 > AFAICT, the release process is standard.[1] > Everything works smoothly except for making the Apache distribution > (when the project is modular). > See issue: > https://issues.apache.org/jira/browse/RNG-31 >=20 > Regards, > Gilles >=20 > [1] See e.g. https://git1-us-west.apache.org/repos/asf?p=3Dcommons-rng.git= ;a=3Dblob;f=3Ddoc/release/release.howto.txt;h=3Dd1d96ed6baa522cb0abedd57e602= 2a819a5a6a01;hb=3DHEAD >=20 >>=20 >> -Rob >>=20 >>>=20 >>> Thanks, >>> Gilles >>>=20 >>>> -Rob >>>>=20 >>>>>=20 >>>>> Regards, >>>>> Gilles >>>>>=20 >>>>> [1] https://issues.apache.org/jira/browse/RNG-31 >>>=20 >>>=20 >=20 >=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