Jars and a classpath with . in it.

Has anyone had a problem accessing package version information when the CLASSPATH environment variable contains . to search the pwd? I was running into a problem where the package versioning information was null unless I removed the . entry in the CLASSPATH. I was not running the JAR with java -jar but instead just including the JAR in the CLASSPATH via java -cp and then specifying the entry point. Once I removed the . from the CLASSPATH the versioning information all worked. This is a problem for me because I need to source a DB2 file that sets up the CLASSPATH to contain the . and I don't think I can get that changed. I didn't think it should necessarily matter because the JAR file I'm using is in the current directory anyway.

Can anyone explain why the CLASSPATH with a . in it would affect the versioning information this way?

[856 byte] By [clappi77a] at [2007-11-26 20:33:24]
# 1

I think I figured this one out, too. I was running the code in my build environment, which meant that the . in the CLASSPATH that preceded my JAR was picking up my app in it's .class form rather than the packaged up JAR form. When I ran my app it had no knowledge of the manifest info since it was run as a class.

clappi77a at 2007-7-10 1:24:43 > top of Java-index,Desktop,Deploying...