Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

>1/ Rename the version so that it's a final one (0.5-SNAPSHOT in 0.5 for
>example). Make sure your changes.xml files are updated and the release date
>mentioned.
>
>2/ Build the projects to produce the artifacts. I guess you'll produce 2
>artifacts: one main jar containing the core classes and the Ant ones and
>another jar which is the Maven plugin for Clirr.
>
>3/ Tag the SCM using your favorite tool (tortoisecvs, eclipse, etc).
>
>  
>

I've done this, built the whole thing, and uploaded the release zips 
(src and bin) to the sf file release system.

>4/ (optional) Publish the 2 jars to the clirr's sourceforge maven
>repository. Honestly I think this should be dropped as it's not useful.
>
>  
>

... and not even permitted by Sourceforge. Here are the terms of 
acceptable use for the web space:

    File releases may not be made available via your project web space
    (unless you have received permission in writing from SourceForge.net
    staff), with the exception of nightly snapshots. File releases
    should be made available using the *File Release System
    <https://sourceforge.net/project/admin/editpackages.php?group_id=89627>*.


>5/ Publish the 2 jars to the ibiblio repository following the instructions
>here: http://maven.apache.org/reference/repository-upload.html
>  
>

Before I do that, could you please make sure that the Maven plugin in 
the binary distribution actually works? I'm not using Maven for anything 
but Clirr, so it's a bit hard for me to test the plugin.

Thanks,
Lars