Clirr.
Clirr is a tool that checks Java libraries for binary 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 incompatib....
Here is the list of declaration for clirr-core. If you use Maven you can use the following code to add the dependency for this POM file.
<dependency> <groupId>net.sf.clirr</groupId> <artifactId>clirr-core</artifactId> <version>0.6</version> </dependency>
If you think this Maven repository POM file listing for clirr-core is inappropriate, such as containing malicious code/tools or violating the copyright, please email info at java2s dot com, thanks.
The clirr-core-0.6 has 4 dependencies.The most popular ones are listed in the following table along with their categories and number of artifacts depending on them.
Category | Artifact | Depended By Count |
---|---|---|
Console | commons-cli 1.0 Commons CLI provides a simple API for working with the command line arguments and options. | 131 |
The following packages are defined in the clirr-core-0.6.jar
net.sf.clirr.ant net.sf.clirr.cli net.sf.clirr.core net.sf.clirr.core.internal net.sf.clirr.core.internal.bcel net.sf.clirr.core.internal.checks net.sf.clirr.core.spi
Here is the content of the POM file.
<?xml version="1.0" encoding="ISO-8859-1"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>net.sf.clirr</groupId> <artifactId>clirr-core</artifactId> <name>Clirr</name> <version>0.6</version> <!-- details about the organization that 'owns' the project --> <organization> <name>Lars K?hne</name> <url>mailto:clirr-devel@lists.sourceforge.net</url> </organization> <inceptionYear>2003</inceptionYear> <description> Clirr is a tool that checks Java libraries for binary 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. </description> <url>http://clirr.sourceforge.net/</url> <issueManagement> <system>sourceforge</system> <url>https://sourceforge.net/tracker/?group_id=89627&atid=590799</url> </issueManagement> <scm> <connection>scm:cvs:pserver:anonymous@cvs.sourceforge.net:/cvsroot/clirr:clirr/core</connection> <url>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/clirr/core</url> </scm> <mailingLists> <mailingList> <name>clirr-user</name> <subscribe>http://lists.sourceforge.net/lists/listinfo/clirr-user</subscribe> <unsubscribe>http://lists.sourceforge.net/lists/listinfo/clirr-user</unsubscribe> <archive>http://lists.sourceforge.net/lists/listinfo/clirr-user</archive> </mailingList> <mailingList> <name>clirr-devel</name> <subscribe>http://lists.sourceforge.net/lists/listinfo/clirr-devel</subscribe> <unsubscribe>http://lists.sourceforge.net/lists/listinfo/clirr-devel</unsubscribe> <archive>http://lists.sourceforge.net/lists/listinfo/clirr-devel</archive> </mailingList> </mailingLists> <contributors> <contributor> <name>Stephen Colebourne</name> <organization>Apache Software Foundation</organization> </contributor> </contributors> <dependencies> <dependency> <groupId>bcel</groupId> <artifactId>bcel</artifactId> <version>5.1</version> </dependency> <dependency> <groupId>ant</groupId> <artifactId>ant</artifactId> <version>1.5.3-1</version> <optional>true</optional> </dependency> <dependency> <groupId>commons-cli</groupId> <artifactId>commons-cli</artifactId> <version>1.0</version> <optional>true</optional> </dependency> <dependency> <groupId>commons-lang</groupId> <artifactId>commons-lang</artifactId> <version>1.0.1</version> <optional>true</optional> </dependency> </dependencies> </project>