jboss-4.2.0.CR1.zip as available at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=491475 shows the same information for many of the JAR files, in fact referring to the version of JBoss AS rather than the version of those specific JARs.

For example:

<jar name="antlr.jar"
specVersion="4.2.0.CR1"
specVendor="JBoss (http://www.jboss.org/)"
specTitle="JBoss"
implVersion="4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200703051212)"
implVendor="JBoss Inc."
implTitle="JBoss [Trinity]"
implVendorID="http://www.jboss.org/"
implURL="http://www.jboss.org/"
sealed="false"
md5Digest="a107fc899a0c4a329cc04f8938fd607b"/>

Reading the following Javadoc I guess this is caused by missing MANIFEST information in the third-party libraries. Therefore, some other means of telling which versions are used would be appreciated very much!

http://fisheye.jboss.com/browse/JBoss/build/jboss/VersionRelease.java?r=1.5
/** A utility which goes through a standard dist build and tags every jar

• with the current build version using the jar file version manifest
• headers. The unique jars and their version info and md5 digests are
• output to the jboss.home/jar-versions.xml.
• @author Scott.Stark@jboss.org
• @version $Revision: 1.5 $
  */
  public class VersionRelease
  {
  :
  }

Thanks,
Arjan.