UCC-J Version 2017.01

USC CSSE and IAI worked together to redo UCC's architecture, and begin implementation in Java this past year! Though not all of the features that exist in the C++ version of UCC is yet implemented in UCC-J, we are making it available to users to begin testing and using it. Once we match UCC-J's functionality to the C++ version, we will begin phasing out the C++ version.

Available Features

  • Counting Capabilities (some discrepancies between UCC-J and UCC still exist, but we are working on removing these)
  • Differencing Capabilities
  • Duplicate Matching
  • Complexity Count
  • Cyclomatic Complexity Count


The features that are not yet implemented in UCC-J are:

  • multiple threads
  • visual differencing
  • legacy output report types
  • -ramlimit
  • -nouncounted
  • -nowarning
  • CC4 results
  • COBOL and Objective C counting and differencing


Release: UCC-J 2017.01 (January 2017) - Download Source



8 comments on “UCC-J Version 2017.01
  1. Tom Konantz says:

    I think I had affiliate status at one time because Northrop Grumman is/was an affiliate. Is that still true? I considered checking the Affiliate box in my Profile, but I’m not certain that it still applies.

  2. Paul Cymerman says:

    When will the C++ version be phased out?

    • Anandi Hira says:

      Hi Paul,

      We are working on making UCC-Java have all of the same features as UCC, at which point we will phase out the C++ version.

      Anandi Hira

  3. Philip Tripp says:

    Where are the checksums published for the UCC-J download package?

    • Anandi Hira says:


      I am not clear on your question. Are you looking for something specific with regards to “checksums”, or do you mean the package itself? I will be attempting to release the old versions to the public next week, and new versions for Affiliates at the same time. I apologize for the delay!

      Anandi Hira

      • Philip Tripp says:

        Typically when software is published, the author(s) will generate a checksum and post it as part of the download (MD5, SHA1, SHA256, etc.). This allows those downloading the software to generate a checksum on their downloaded software, and verify the integrity of the software (i.e. it has not been altered, maliciously or otherwise, from the author(s) original form).

        This is an industry standard practice.

        Additional reference:

        • Anandi Hira says:


          Thank you for explanation. We currently do not provide checksums as part of the download, but is something we can look into for future releases!

          Thank you,
          Anandi Hira

Leave a Reply