Releasing

Quick notes for developers wanting to release a version of LSC.

Make sure a branch is ready for release. This must involve testing by automated tests and a call for testing by developers and willing users.

Update the CHANGES file in lsc-sample and lsc. It is the same file, so just copy it from one to the other once it's updated. It can be reconstructed from the detail of a version in Redmine, for example: http://tools.lsc-project.org/versions/show/4

Then, tag a version in SVN:

$ svn cp lsc/branches/v1.1/ lsc/tags/1.1.0
$ svn cp lsc-sample/branches/v1.1/ lsc-sample/tags/1.1.0

Edit the version number in lsc-core pom.xml:

$ vi lsc/tags/1.1.0/pom.xml
[...]
        <artifactId>lsc-core</artifactId>
        <name>Ldap Synchronization Connector</name>
        <version>1.1.0</version>
[...]

Edit the version number in lsc-sample pom.xml and dependency version:

$ vi lsc-sample/tags/1.1.0/pom.xml
[...]
    <artifactId>lsc-sample</artifactId>
    <name>Ldap Synchronization Connector Sample</name>
    <version>1.1.0</version>
[...]
        <dependency>
            <groupId>org.lsc</groupId>
            <artifactId>lsc-core</artifactId>
            <version>1.1.0</version>
        </dependency>
[...]

Last but not least, commit this tag:

$ svn commit -m"Tagging 1.1.0 for release" lsc-sample/tags/1.1.0 lsc/tags/1.1.0

Build with

ant lsc::dist

and copy the target/lsc-*-1.1.0.tar.gz files to be distributed.

Run

mvn deploy

in lsc-core to deploy the lsc-core-1.1.0.jar file to the Maven repo.