My Schedule

Speaking

EclipseWorld

October 28 - 30 - Presenting two sessions on OSGi.

Events

JavaOne

May 6 - 9 - Attending JavaOne in San Francisco.

The opinions expressed on this site are my own, and not necessarily those of my employer.

Aug '07
3

JarAnalyzer Upgrade

Filed Under Metrics, Java, Platforms, Architecture & Design |  

I’ve updated JarAnalyzer to correct some of the problems reported when analyzing applications written on J2SE 5.0. The issues were primarily surrounding the use of Generics. If you’ve been experiencing any of the following problems when running JarAnalyzer 1.1, upgrading to JarAnalyzer 1.2 should make them go away and put you back on track.

  • You receive the following error at the console: Visiting non-standard Signature object. The fix required an upgrade to BCEL 5.2.
  • The xml output lists classes as Unresolved Dependencies. This problem was due to how JarAnalyzer strips the classname from the package the class belongs to.

A few other bug fixes and enhancements also found their way into version 1.2.

  • Used System properties file separator to increase portability across operating systems.
  • Updated filter.properties file to ignore packages you typically don’t want reported as Unresolved Dependencies. This can easily be modified before running JarAnalyzer if you want these to show in the output.

You can download the most current version of JarAnalyzer from the JarAnalyzer home.

Comments

2 Responses to “JarAnalyzer Upgrade”

  1. Dr. Dietmar Wolz on December 7th, 2007 10:04 am

    Is there a possibility to find out which
    jar caused the trouble?
    Got hundreds of
    “Visiting non-standard Signature object”
    messages analyzing a directory which contains the jars below. I am using version 1.2.

    Would be a very helpful tool if you could
    resolve the issue.

    activation-1.1.jar
    activeio-core-3.0.0-incubator.jar
    activemq-core-4.1.1.jar
    activemq-ra-4.1.1.jar
    backport-util-concurrent-2.2.jar
    classworlds-1.0.1.jar
    commons-beanutils-core-1.7.0.jar
    commons-logging-1.1.jar
    derby-10.2.2.0.jar
    geronimo-connector-2.0.1.jar
    geronimo-ejb_2.1_spec-1.1.jar
    geronimo-j2ee-connector_1.5_spec-1.1.jar
    geronimo-j2ee-jacc_1.0_spec-1.1.jar
    geronimo-j2ee-management_1.0_spec-1.1.jar
    geronimo-jms_1.1_spec-1.1.jar
    geronimo-jta_1.1_spec-1.1.jar
    geronimo-servlet_2.4_spec-1.1.jar
    geronimo-transaction-2.0.1.jar
    howl-1.0.1-1.jar
    jencks-2.1.jar
    log4j-1.2.13.jar
    mail-1.4.jar
    servicemix-audit-3.2.jar
    servicemix-core-3.2-p1.jar
    servicemix-jbi-3.2.jar
    servicemix-services-3.2.jar
    spring-beans-2.0.6.jar
    spring-context-2.0.6.jar
    spring-core-2.0.6.jar
    spring-dao-2.0.6.jar
    spring-jmx-2.0.6.jar
    stax-api-1.0.1.jar
    woden-1.0.0M6.jar
    wsdl4j-1.6.1.jar
    wstx-asl-3.2.2.jar
    xalan-2.7.0.jar
    xbean-classloader-3.2.jar
    xbean-kernel-3.2.jar
    xbean-server-3.2.jar
    xbean-spring-3.2.jar
    xercesImpl-2.8.1.jar
    xml-apis-1.3.04.jar
    xstream-1.1.2.jar

  2. kirk on December 8th, 2007 6:37 am

    Well that is interesting. I’ll try to look into this sometime soon (can’t promise anything). First thing you might want to check is that you are using the most current version of bcel (5.2).

Leave a Reply




Recently Written

Categories

Archives