We have that same problem (avoiding putting tarballs into maven central). Our current approach does the following:
1) We have specific projects (usually the top level one in multi-module setups) that produce the assembly artifacts. These projects have a deploy configuration override of <skip>true</skip> which prevents deployment of the tarballs. 2) Deploy is where normally the md5 and sha1 checksums are produced, so we add a step for these projects to produce those, using the antrun pluging with the "checksum" element. You can see this here: https://svn.apache.org/repos/asf/uima/build/trunk/parent-pom/pom.xml line# approx: 1200 Cheers. -Marshall On 4/2/2013 12:31 AM, Stefan Bodewig wrote: > On 2013-03-31, Robert Burrell Donkin wrote: > >> The candidate staged at >> https://repository.apache.org/content/repositories/orgapachecreadur-039/ >> (orgapachecreadur-039) is ready for review. Please download, check and >> then cast your vote (see [1]). > Do you intend to move the distribution tarballs to www.apache.org/dev? > Can't recall whether we are already using svnpubsub for releases. > > Personally I'm not fond of putting the tarballs into Maven central at > all but haven't found a way to avoid it myself either (I usually remove > them manually before closing the staging repository). > > Stefan >
