Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-JSR-4
-
Fix Version/s: 1.1-beta-1
-
Component/s: None
-
Labels:None
-
Environment:Windows XP, Java 1.5.0_06
Description
The script:
import does.not.exist
new Foo()
produces the error:
CommandLine.groovy: 3: unable to resolve class Foo
@ line 3, column 1.
It would be helpful if it mentioned that the package/class in the import line couldn't be found, for the case where Foo() is imported from there.
It's more useful when you import with wildcards:
import a.b.*
new Foo()
If the error is on the "new Foo()" line, you may think that it imported the package ok, and check for spelling errors in Foo or check which package Foo is really in.