Return-Path: Delivered-To: apmail-incubator-river-dev-archive@minotaur.apache.org Received: (qmail 63905 invoked from network); 5 Aug 2009 07:06:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Aug 2009 07:06:42 -0000 Received: (qmail 51338 invoked by uid 500); 5 Aug 2009 07:06:49 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 51269 invoked by uid 500); 5 Aug 2009 07:06:49 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 51259 invoked by uid 99); 5 Aug 2009 07:06:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2009 07:06:49 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jeff.ramsdale@gmail.com designates 209.85.198.243 as permitted sender) Received: from [209.85.198.243] (HELO rv-out-0708.google.com) (209.85.198.243) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2009 07:06:40 +0000 Received: by rv-out-0708.google.com with SMTP id f25so1389271rvb.0 for ; Wed, 05 Aug 2009 00:06:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=sIQRKcm1d+5Mhl/tIdFtEZBq2ONPkN4aVIZV6P1WcX8=; b=xph/ZQD6cWie7IYT8LUig+YymtaCvgsyiS9YpDk48KFQvzB9R2tRt2VH+BwjPzBAWS NXENOkfvLXq7emAIfNqCM9y5zWj/oBcWyCR2wWol1SU5EQpjPW5PPxEu/CdR3IVyJQ0X OoA/MFx1e2Q6DyIhLQRYsrGhF+YOeDgZbuajA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=k0W4tfUoPLOxrBkmj+KGhNQOSRBxSXChGiOiGSgKfoIxOk4JAGTE69OyPs8pjC2ndi uiefQEq5M4y8t7vGaeTxpPT1sI2L05VKOToqip7Nt5IBfBjEYYfjXxYqOZk40aoSUclf Biwt7oN6e1Toj7SZTp7haojSXGUahFdV3bo8U= MIME-Version: 1.0 Received: by 10.140.225.10 with SMTP id x10mr5881575rvg.65.1249455978998; Wed, 05 Aug 2009 00:06:18 -0700 (PDT) Date: Wed, 5 Aug 2009 00:06:18 -0700 Message-ID: Subject: Artifacts in Maven From: Jeff Ramsdale To: river-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=000e0cd21722ca6d4c04705fa3a5 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd21722ca6d4c04705fa3a5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Would others see a benefit to deploying the Apache River artifacts to the central Maven repository upon a successful Hudson build (i.e. SNAPSHOTs)? Even better, when AR2 is released? I'm sure the Maven Jini Plugin, Maven Classdep Plugin and Rio (to pick several examples) could benefit from having those managed by this community rather than independently. How difficult would this be to add to the current release process? -jeff --000e0cd21722ca6d4c04705fa3a5--