My Stuff

2010 Conferences

OSGi DevCon @ JAX London

February 23 - Keynote titled OSGi in the Enterprise: Agility, Modularity, and Architecture’s Paradox

EclipseCon

March 22 - 25 - Tutorial on Modular Architecture

Über Conf

June 14 - 17 - Sessions titled Turtles and Architecture and Patterns of Modular Architecture

Catalyst

July 26 - 30 - Two sessions on rich mobile applications and one on agile development. Half day tutorial on software process improvement.

Tweets @ Twitter

Gearing up for lots of conversation today. Mobile dev., app arch., and some questions for @springrod. Plus a video shoot. #cat10 22 hrs ago

Great feedback on RMA sessions at #cat10 today. Lot's of fun. Look forward to more interaction on the topic tomorrow (and tonight perhaps)! 1 day ago

.@atmanes Did I say "process"? Meant "progress". in reply to atmanes 1 day ago

RT @dalmaer RT @lukew: Comic: the real reason you should design for Mobile First! http://bit.ly/bhKSV6 #thanksron 1 week ago

anyone know if current webOS version (1.4.1.1?) fixes the aGPS problem on Verizon? Does Google Maps lockin the location efficiently? 1 week ago

LinkedIn Profile

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

Aug '07
3

JarAnalyzer Upgrade

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

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

5 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).

  3. Bernd Eckenfels on September 29th, 2008 11:08 am

    Kirk, you asked for some feedback on JarAnalyzer, so here are my few cents:

    - I like JAR Analyzer, the following features would be helpfull to me:

    - in the “UnresolvedDependencies” section not only list the names of the packages you did not found, but also the names of the packages or classes which used those

    - make all sections absent in the xml if empty

    - for the outgoing dependencies it would be interesting for me to differentiate the kind of usage. Especially “EI” (Extends Interface) and “EC” (Extends Class) and “EA” (Extends Abstract Class) would be interesting. This can be for example used to check that you are not extending any GPL’ed class:

    SomeGPL.jar

    …

    - would be good if JAR Analyser could traverse WAR/EAR/SAR archives

    - An ANT/Junit mode where i can specify assertions (like JDepend). So I can say “fail this build if any new dependency was added”. This is especially helpfull with the added features above.

    Greetings
    Bernd

  4. Crazy90 on October 23rd, 2009 1:40 am

    And work faster with dynamically updated cross-references, improved variable-data publishing, and automatic page addition and deletion. ,

  5. EdgeWiseInAnnArbor on March 25th, 2010 3:09 pm

    I know this is super old, and chances are you will not read this, but I’d love an optional report that tells you what the dependencies are caused by. I want to remove a particular jar file dependency, and find what needs it and remove it, and knowing Class X depends on jar Y, Class Z would be useful for removing jar Y.

Leave a Reply




Modularity Patterns

Recently Written

Categories

Archives