Hi Chris,

there is a quite detailed explanation of what Apache understands as a release:

  http://www.apache.org/dev/release.html

Uploading the source JARs to Maven Central is afaik not enough. 
What UIMA does is, we set up the build so that as part of the Maven build,
a ZIP of the checked out sources is done starting from the root of the checkout.
It's actually pretty straight. I believe this ZIP is augmented with some
license files etc. As part of the release this source ZIP and a corresponding
ZIP containing a compiled distribution are uploaded to the Apache mirror system.

If you would like to take Apache UIMA as a role model, check out our release 
guidelines:

  http://uima.apache.org/release.html

And of course our Maven-based build setup which helps us in doing the releases
is in the Apache SVN.

Cheers,

-- Richard

On 11.11.2014, at 10:23, Christofer Dutz <christofer.d...@c-ware.de> wrote:

> Hi,
> 
> at the Flex project there are some parts being built with Maven. Now we would 
> like to release some of them and currently there is a bit of a discussion 
> about how to do this. Currently most people are insisting on a rather manual 
> process they have been using for releasing the Ant built stuff.
> 
> Now I think maven could make life a lot easier for us, but I don't quite know 
> how to comply to the Apache release rules. I think simply releasing the 
> auto-generated source jars isn't what Apache understands as Source release.
> 
> I guess you on this list have a lot of experience with releasing Maven built 
> Apache projects. Would be glad for some pointers. Searching the Maven 
> Confluence page doesn't guide me to release documentations dealing with the 
> requirements of the ASF and even mentioning "apache maven and release" swamps 
> me with maven-release-plugin documentation ;-)
> 
> Would be grateful for some links or clarification.
> 
> Chris


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to