I wrote: >The version is included in the manifest information in the jar file >in the specification-Version property under the org/apache/oro section. ... >assembled. Off the top of my head I can't tell you how to get at it >from a program, but the functionality exists.
Here's the manifest from a build sitting on my hard drive. Worst case you can extract the version with a regular expression :) Manifest-Version: 1.0 Ant-Version: Apache Ant 1.5.3 Created-By: 1.4.2-b28 (Sun Microsystems Inc.) Name: org/apache/oro Specification-Title: Jakarta ORO Specification-Version: 2.0.8 Specification-Vendor: Apache Software Foundation Implementation-Title: org.apache.oro Implementation-Version: 2.0.8 2004-02-14 01:17:05 Implementation-Vendor: Apache Software Foundation If anyone wants to offer reasons for adding an org.apache.oro.Version class, we can discuss it on oro-dev. The one reason I can think of is to work around the the presence of older jakarta-oro jars in some of the major application servers that conflict with more recent versions used by application developers. But there's a lot of software like that and I can't imagine that it's practical to test the version of each package and use a different classloader when the version isn't acceptable. daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
