tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Meikle" <loo...@gmail.com>
Subject Re: Tika 0.2 Release Plan
Date Mon, 17 Nov 2008 23:33:29 GMT
2008/11/17 Jukka Zitting <jukka.zitting@gmail.com>

> Personally I'd just go for a packaged svn export as the source release
> and the normal Maven build artifact (tika-0.2.jar) as the binary
> artifact. This way the source we release would be the bits that we
> have worked on and tagged in SVN instead of a build artifact, however
> similar those may be in practice.

Looking at this, I think I prefer the way you have described as well.

> No, that would be /www/www.apache.org/dist/lucene/tika (I just created
> the directory).
> The m2-ibiblio-rsync-repository is a way for us to publish release
> artifacts to the central Maven repository. There are a few ways to
> handle publishing of Maven release artifacts; one way is to "mvn
> deploy" the release candidate to an empty staging repository for
> review during the release vote. Once the vote has passed, the staged
> artifacts can then be copied to
> /www/people.apache.org/repo/m2-ibiblio-rsync-repository on
> people.apache.org, from where they will be automatically synced to the
> central Maven repository.

Excellent, thanks for this.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message