Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.5.1
-
Fix Version/s: 1.6-rc-2
-
Component/s: None
-
Labels:None
-
Environment:ubuntu linux, sun-java-6; also duplicated on windows/cygwin java1.5
-
Number of attachments :
Description
The following 2-line script will run if called with an absolute path, but fails if called as ../bin/scriptName
Here's the script:
#!/usr/bin/env groovy
println("Yo!");
This may be an example of GROOVY-569, since renaming the script to have a .gr suffix seems to solve the problem.
I wasn't aware until reading GROOVY-569 that script names must have a dot!
This is very confusing: script names actually don't require a dot except in limited circumstances.
I've been using groovy for a year or so, and this is the first I've encountered this requirement. The "Groovy in Action"
book doesn't seem to mention this requirement, although all their examples seem to use .groovy suffix, so maybe it's in there somewhere.
I'm a keyboard junkie (100+ words per minute) and would like to be able to create short concise names for all my scripts, not
just bash / perl / etc. Scripting languages (at least in unix land).
For the sake of script developers coming from other languages, it would be preferable to strictly enforce this naming requirement in every case (e.g., "illegal script name: filename suffix is mandatory"), since it's very difficult to track down the cause of this problem. A frustrated developer is not likely to be searching for the phrase "script name" if the symptoms are relative to absolute versus relative path used with calling a script.
BTW, groovy rocks!
Issue Links
| This issue duplicates: | ||||
| GROOVY-569 | java.lang.ClassFormatError running groovy script from shell (bash) |
|
|
|
Activity
The script:
#! /usr/bin/env groovy
// -*- mode:groovy encoding:UTF-8 -*-
println ( 'Hello World' )
has the execute bit set so can be executed as a command (on a proper operating system anyway 
This script executes fine using the command lines:
GROOVY_569 ./GROOVY_569
assuming you are in the directory in which the script is. Even:
/home/users/russel/Progs/OddsByLanguage/Groovy/GROOVY_569
seems to work fine. However:
../Groovy/GROOVY_569
generates the original error:
Caught: java.lang.NoClassDefFoundError: /
at ..class$(GROOVY_569)
at ..get$class$$(GROOVY_569)
at ..<clinit>(GROOVY_569)
I am therefore reopening this bug.
#! /usr/bin/env groovy
// -*- mode:groovy encoding:UTF-8 -*-
println ( 'Hello World' )
This script executes fine using the command lines:
GROOVY_569 ./GROOVY_569
/home/users/russel/Progs/OddsByLanguage/Groovy/GROOVY_569
../Groovy/GROOVY_569
Caught: java.lang.NoClassDefFoundError: /
at ..class$(GROOVY_569)
at ..get$class$$(GROOVY_569)
at ..<clinit>(GROOVY_569)
I created a small hierarchy:
.
|-- bin
| `-- scriptName
\`-- location
and if scriptName is execute from the directory bin or by absolute path then it works fine. If called using ../bin/scriptName from location then:
Caught: java.lang.NoClassDefFoundError: /
at ..class$(scriptName)
at ..<clinit>(scriptName)
I think this should be considered a blocker. I will raise the priority on this. If I have misunderstood or got something wrong, the change can be reverted.