Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Won't Fix
-
1.7.5
-
None
-
None
-
None
Description
Consider the following script
println org.apache.log4j.Category.class
Save it as cp.groovy in a directory where the log4j jar isn't present (You can replace the log4j class with any class available in a jar that's handy, the issue is not specific to log4j and I've tested it with different libraries)
Let's put the log4j library in c:\log4j-1.2.14.jar and invoke the script, setting the classpath:
C:\work>groovy -cp c:\log4j-1.2.14.jar cp.groovy
class org.apache.log4j.Category
Now add another directory at the beginning of the classpath (a directory where, of course, the jar isn't present).
C:\work>groovy -cp c:\temp;c:\log4j-1.2.14.jar cp.groovy
Caught: groovy.lang.MissingPropertyException: No such property: org for class: cp
at cp.run(cp.groovy:1)
The library is not recognized (and thus Groovy treats the fully qualified name as a chain of property accesses). I monitored file access with Sysinternals' FileMon and there's no attempt to read second jar.
Attachments
Issue Links
- is related to
-
GROOVY-5624 groovy.bat/startGroovy.bat destroys -cp class path that contains dashes in file names
- Closed