This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

This page describes how one can use Clirr with Shade to compare components that have changed packages.

Clirr compares different versions of classes with the same package name Shade can be used to change package names throughout a jar file By combining the two, it is possible to use Clirr to check classes that are now in a new package.

The process is:

  • use Shade to convert the old package names to the new package names
  • install the shaded jar in the local repository
  • run Clirr against the shaded jar

Here is a sample POM (shade.xml) for comparing org.apache.bcel:bcel:5.2 against org.apache.commons:commons-bcel6:6.0

<project xmlns="" xmlns:xsi=""

  <!-- New Maven co-ordinates -->
  <name>Commons BCEL shader</name>
  This POM can be used to install a shaded version of BCEL 5.2
  in the local repo. Usage:

  mvn -f shade.xml install

  You can then run Clirr using the default POM:

  mvn clirr:clirr

    <!-- Ensure local files are not compiled -->
    <!-- Source jar -->
      <!-- Exclude all dependencies, we don't want them in the shaded jar -->
              <!-- specify old and new base package names -->
  • No labels