lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: discussion about release frequency.
Date Sat, 18 Sep 2010 20:18:14 GMT
Hi Robert,

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

The long and the short of it is that there are several canonical Maven repos that are sync'ed
to Ibiblio and Maven central. Apache has one (through, 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 release jars through the Sonatype JIRA process,
located here:

Guide is here:

Hope that helps!


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 representative 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 separate concern?

I'm not sure how complicated actually upload artifacts is, although just browsing other projects,
getting maven releases out isn't exactly a walk in the 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 must be to an
<>  location?)

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

View raw message