Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 97451 invoked from network); 18 Sep 2010 20:18:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Sep 2010 20:18:45 -0000 Received: (qmail 3914 invoked by uid 500); 18 Sep 2010 20:18:44 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 3871 invoked by uid 500); 18 Sep 2010 20:18:43 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 3864 invoked by uid 99); 18 Sep 2010 20:18:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Sep 2010 20:18:43 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [128.149.139.105] (HELO mail.jpl.nasa.gov) (128.149.139.105) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Sep 2010 20:18:38 +0000 Received: from mail.jpl.nasa.gov (altvirehtstap01.jpl.nasa.gov [128.149.137.72]) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id o8IKIGhJ017081 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified FAIL) for ; Sat, 18 Sep 2010 13:18:16 -0700 Received: from ALTPHYEMBEVSP20.RES.AD.JPL ([128.149.137.82]) by ALTVIREHTSTAP01.RES.AD.JPL ([128.149.137.72]) with mapi; Sat, 18 Sep 2010 13:18:16 -0700 From: "Mattmann, Chris A (388J)" To: "dev@lucene.apache.org" Date: Sat, 18 Sep 2010 13:18:14 -0700 Subject: Re: discussion about release frequency. Thread-Topic: discussion about release frequency. Thread-Index: ActXbXHxN7MqC/OQT0KX4X/ETXdhlQAAS1OJ Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C8BA6C961ECE3ChrisAMattmannjplnasagov_" MIME-Version: 1.0 X-Source-IP: altvirehtstap01.jpl.nasa.gov [128.149.137.72] X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized --_000_C8BA6C961ECE3ChrisAMattmannjplnasagov_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Robert, I can help a little here. Check out this guide: http://maven.apache.org/guides/mini/guide-central-repository-upload.html The long and the short of it is that there are several canonical Maven repo= s that are sync'ed to Ibiblio and Maven central. Apache has one (through re= pository.apache.org), and other organizations have em' too. In Tika, we sim= ply inherit from the top level Apache POM and the Maven release plugin take= s care of the rest. I'm not sure how to do this with Ant, but am sure it ca= n be done (and it might be aided by Ivy). If you are just doing it when you release, which doesn't happen that often,= then you could consider just creating a Ticket and uploading the release j= ars through the Sonatype JIRA process, located here: http://nexus.sonatype.org/oss-repository-hosting.html Guide is here: https://docs.sonatype.org/display/repository/sonatype+oss+maven+repository+= usage+guide Hope that helps! Cheers, Chris On 9/18/10 1:08 PM, "Robert Muir" wrote: On Sat, Sep 18, 2010 at 3:57 PM, Steven A Rowe wrote: Last time I checked, maven artifacts have to be uploaded by a representativ= e of the project. I.e. a committer. Farming this out seems like a no-go (= for good reasons). - Steve Well, (again completely ignorant of maven) it seems this itself is a separa= te concern? I'm not sure how complicated actually upload artifacts is, although just br= owsing other projects, getting maven releases out isn't exactly a walk in t= he park. but theres two steps right? 1. generating the actual artifacts and verifying they are correct 2. uploading the artifacts (e.g. commit or whatever it takes to do that) Why exactly does it require a committer to upload maven artifacts (they mus= t be to an apache.org location?) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: Chris.Mattmann@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --_000_C8BA6C961ECE3ChrisAMattmannjplnasagov_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: discussion about release frequency. Hi Robert,

I can help a little here. Check out this guide:

http://maven.apache.org/guides/mini/guide-central-repository-uplo= ad.html

The long and the short of it is that there are several canonical Maven repo= s that are sync’ed to Ibiblio and Maven central. Apache has one (thro= ugh repository.apache.org), and other organizations have em’ too. In = Tika, we simply inherit from the top level Apache POM and the Maven release= plugin takes care of the rest. I’m not sure how to do this with Ant,= but am sure it can be done (and it might be aided by Ivy).

If you are just doing it when you release, which doesn’t happen that = often, then you could consider just creating a Ticket and uploading the rel= ease jars through the Sonatype JIRA process, located here:

http://ne= xus.sonatype.org/oss-repository-hosting.html

Guide is here:

https://docs.sonatype.org/display/repository/sonaty= pe+oss+maven+repository+usage+guide

Hope that helps!

Cheers,
Chris

On 9/18/10 1:08 PM, "Robert Muir" <rcmuir@gmail.com> wrote:


On Sat, Sep 18, 2010 at 3:57 PM, Steven A Rowe <sarowe@syr.edu> wrote:
Last time I checked, ma= ven artifacts have to be uploaded by a representative of the project.=A0 I.= e. a committer.=A0 Farming this out seems like a no-go (for good reasons). = - Steve
=A0

Well, (again completely ignorant of maven) it seems this itself is a separa= te concern?

I'm not sure how complicated actually upload artifacts is, although just br= owsing other projects, getting maven releases out isn't exactly a walk in t= he park.

but theres two steps right?
1. generating the actual artifacts and verifying they are correct
2. uploading the artifacts (e.g. commit or whatever it takes to do that)
Why exactly does it require a committer to upload maven artifacts (they mus= t be to an apache.org <http://apache.org>  location?)


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: C= hris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 --_000_C8BA6C961ECE3ChrisAMattmannjplnasagov_--