Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0m2
-
Fix Version/s: 2.0.0RC1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
When Groovy is run on the command-line, it automatically picks up any jars in your .groovy/lib directory.
It is desirable to have this behavior in the plugin as well, so that the results are the same when running in Eclipse or on the commandline.
Current workaround in Eclipse is to add the libraries manually, one by one.
Issue Links
- relates to
-
GRECLIPSE-789
Problem Launching Groovy Console or Running as Groovy Script in Eclipse 3.5.2
-
I'd imagine RunAs groovy script will do this automatically (or at least it should do...)
For RunAs application, we probably have to decide whether to pull them in when the project is defined if it is pointing to a new set of resources. Or we provide an easy context menu action on a groovy project 'Import groovy libs' or somesuch that will do what you currently have to do manually. I'm not so sure about it scanning repeatedly watching for changes (unless groovy libs is going to be a folder under our eclipse control), but if we can make it easy to sync up the project with the current state of groovy libs, maybe that is good enough.
What happens here may be influenced by that other bug on the work directory.