From dev-return-165878-archive-asf-public=cust-asf.ponee.io@commons.apache.org Thu Jan 4 14:41:11 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 53791180657 for ; Thu, 4 Jan 2018 14:41:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4301F160C2B; Thu, 4 Jan 2018 13:41:11 +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 6204A160C28 for ; Thu, 4 Jan 2018 14:41:10 +0100 (CET) Received: (qmail 4375 invoked by uid 500); 4 Jan 2018 13:41:09 -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 4363 invoked by uid 99); 4 Jan 2018 13:41:08 -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 13:41:08 +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 73237C2C22 for ; Thu, 4 Jan 2018 13:41:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.72 X-Spam-Level: X-Spam-Status: No, score=-0.72 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=scarlet.be Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id syRwcGNfwFlf for ; Thu, 4 Jan 2018 13:41:06 +0000 (UTC) Received: from sif.is.scarlet.be (sif.is.scarlet.be [193.74.71.28]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 46A965F576 for ; Thu, 4 Jan 2018 13:41:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scarlet.be; s=scarlet; t=1515073266; bh=/RfLVggG+1SwUYRHteS8k+ni/oS8OyEuhNeVJ9YIhM0=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To: Subject:In-Reply-To:References:Message-ID; b=kdR7eGZt6U4XUwA00S/uvNRJHXmMbtJ8hcXk9fug/q6fZ0XampcLeO5RiSkY9VeMt RYE/sxn7GVhWqys3HVqi0K1VoiNiTMZ2U7V8xRJyYit7qVp6rbx1l/JfneM20Soabv 2zNqfusqJ2wX17xb+SJubWOxrzD2hjUZMs8/HpYM= Received: from webmail.scarlet.be (gresham.is.scarlet.be [193.74.71.215]) by sif.is.scarlet.be (8.14.9/8.14.9) with ESMTP id w04Df5sc030505 for ; Thu, 4 Jan 2018 14:41:06 +0100 X-Scarlet: d=1515073266 c=193.74.71.215 Received: from ip-213-49-200-45.dsl.scarlet.be ([213.49.200.45]) via ip-213-49-200-45.dsl.scarlet.be ([213.49.200.45]) by webmail.scarlet.be with HTTP (HTTP/1.1 POST); Thu, 04 Jan 2018 14:41:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 04 Jan 2018 14:41:05 +0100 From: Gilles To: Subject: Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/) In-Reply-To: <2CCA990F-5611-433B-9888-F6A56079FAEB@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> Message-ID: <0415812331dd66d49ec9a53a1a6cc845@scarlet.be> X-Sender: gilles@harfang.homelinux.org User-Agent: Scarlet Webmail X-DCC-scarlet.be-Metrics: sif; whitelist X-Virus-Scanned: clamav-milter 0.98.1-exp at sif X-Virus-Status: Clean On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: >> On Jan 4, 2018, at 5:24 AM, Gilles >> wrote: >> >> Hi. >> >> On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: >>> Hello all, >>> >>> 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: >>> >>> mvn clean site deploy -Prelease -Duser.name=chtompki >>> -Duser.password= >>> >>> Thoughts on pulling this in as a new component and starting to get >>> it >>> to a more formal state? I’m sure we could add more, but this does >>> take >>> away a considerable portion of the manual steps. >> >> Does it work for modular components? [See below.] >> >>> Also, as I said before I’ve not written any maven unit/integration >>> 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. >>> >>> Should I call a vote for the new component? >>> >>> Cheers, >>> -Rob >>> >>> >>> >>>> On Jan 3, 2018, at 8:59 PM, chtompki@apache.org wrote: >>>> >>>> Author: chtompki >>>> Date: Thu Jan 4 01:59:44 2018 >>>> New Revision: 24003 >>>> >>>> Log: >>>> Removing commons-text-1.3-SNAPSHOT >>>> >>>> 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 >>>> >> >> 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. >> >> 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. > > Yes. Your have a good point point Gilles. > > It would seem that we would want some flavour of a new distribution > handling mojo for just this case, but I don’t foresee that as being > overly difficult, we’d have to just accommodate for a slightly more > 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. > > Thoughts? Why "more manual process"? Is the modular case any different from the maven API POV (I'd imagine it's "just" building recursively)? 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. Thanks, Gilles > -Rob > >> >> Regards, >> Gilles >> >> [1] https://issues.apache.org/jira/browse/RNG-31 >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org