[Clirr-devel] CVS: clirr project.xml,1.29,1.30
Status: Alpha
Brought to you by:
lkuehne
From: <lk...@us...> - 2006-03-18 20:25:55
|
Update of /cvsroot/clirr/clirr In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20652 Modified Files: project.xml Log Message: added version 0.6, changed curret version to 0.7-dev. Also mention source compatibility in project description Index: project.xml =================================================================== RCS file: /cvsroot/clirr/clirr/project.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- project.xml 19 Sep 2005 13:15:26 -0000 1.29 +++ project.xml 18 Mar 2006 20:25:52 -0000 1.30 @@ -14,7 +14,7 @@ <!-- The version of the project under development, e.g. 1.1, 1.2, 2.0-dev --> - <currentVersion>0.6</currentVersion> + <currentVersion>0.7-dev</currentVersion> <!-- details about the organization that 'owns' the project --> <organization> @@ -27,17 +27,17 @@ <package>net.sf.clirr</package> <logo>/images/clirr.png</logo> <description> - Clirr is a tool that checks Java libraries for binary + Clirr is a tool that checks Java libraries for binary and source compatibility with older releases. Basically you give it two sets of jar files and Clirr dumps out a list of changes in the public api. Clirr provides an Ant task that can be configured to break the build if it detects incompatible api changes. In a continuous integration process Clirr can automatically prevent accidental - introduction of binary compatibility problems in Java libraries. + introduction of compatibility problems in Java libraries. </description> <!-- a short description of what the project does --> <shortDescription> - Java binary compatibility checker + Java compatibility checker </shortDescription> <!-- the project home page --> @@ -76,6 +76,11 @@ <name>0.5</name> <tag>RELEASE_CLIRR_0_5</tag> </version> + <version> + <id>0.6</id> + <name>0.6</name> + <tag>RELEASE_CLIRR_0_6</tag> + </version> </versions> <!-- any mailing lists for the project --> |