Hey Tim,
Thanks, i think the upgrade would be useful. By the way, I knew that JBlanket uses Jdom. :) What my problem report mainly addresses is the fact that if we build Hackystat with JBlanket enabled, it doesn't work. However, the problem comes from the Hackystat build system. I think this has little or nothing to do with JBlanket, per se.
I'll try to explain the problem a little better. These are the contents of the hackyBuild/lib/ant directory:
- checkstyle-all-3.1.jar - checkstyle-noframes.xsl - hackyLoadTest.ant.jar - j2h.jar - j2htaskdef.jar - jblanket.jar - junit.jar - locc.jar - sensor.bcml.jar - sensor.build.jar - sensor.cppunit.jar - sensor.dependencyfinder.jar - sensor.jblanket.jar - sensor.jira.jar - sensor.junit.jar - sensor.loadtest.jar - sensor.locc.jar - sensorshell.jar
Jar files like jblanket.jar, locc.jar, sensor.locc.jar depend on JDOM. But, you'll see that jdom.jar is not in this directory. Hmm.. The lack of jdom.jar suggests that Hackystat developers should download jdom.jar file separately and install it in the ANT_HOME/lib. But, that isn't totally true, because sensorshell.jar contains Jdom 1.0 (this was a very recent change). Locc just got recently upgraded to Jdom 1.0, so we are safe there. But, JBlanket uses beta 9. Here's a problem. We cannot simply add the Jdom beta 9 jar file to the ANT_HOME/lib either, because of classpath problems.
I would suspect that we update the DailyBuild with the new sensorshell, locc, and other jar files that now use Jdom 1.0. We might have some problems with Jblanket and any other tools using the old jdom.
thanks, aaron
ps.. this problem serves as a warning... when we do future upgrades we have to ensure that we upgrade all the tools (locc, bcml, jblanket, etc).
At 07:13 PM 3/5/2005, you wrote:
JBlanket does use JDom. The XML files that contain the method information are written using JDom. I haven't converted it to use JDom 1.0. It currently uses beta 9. I'll add a JIRA issue to convert it to 1.0.
