
|
If you were logged in you would be able to see more operations.
|
|
|
If the script file is "Events.groovy", you end up getting an "events" command-line task. This probably isn't intentional, so we should instead use "_Events.groovy" as the file name.
Attached is a patch which will try to use "_Events.groovy", and if it doesn't exist, will use "Events.groovy" and display a warning message to the screen. My suggestion would be to use this, and in 1.1, do away with "Events.groovy" in favor of "_Events.groovy" altogether.
|
|
Description
|
If the script file is "Events.groovy", you end up getting an "events" command-line task. This probably isn't intentional, so we should instead use "_Events.groovy" as the file name.
Attached is a patch which will try to use "_Events.groovy", and if it doesn't exist, will use "Events.groovy" and display a warning message to the screen. My suggestion would be to use this, and in 1.1, do away with "Events.groovy" in favor of "_Events.groovy" altogether. |
Show » |
|