What should be done if a given module (containing Groovy scripts) is already configured with a Groovy library older than the one shipped with the plug-in?
Franck Rasolo added a comment - 05/Apr/05 06:23 PM What should be done if a given module (containing Groovy scripts) is already configured with a Groovy library older than the one shipped with the plug-in?
[1:12pm] sam: fraz: all i think you should do with the plugin is make it easy to add it to their project using files already included with the plugin [1:14pm] sam: fraz: right now you must download more than the plugin to run your groovy scripts [1:16pm] fraz: sam: true, but should it be automatic or through a toggable option? [1:16pm] sam: Fraz: i think it should show up as a global library you can click [1:17pm] sam: can you add it to this list in IDEA? http://homepage.mac.com/spullara?/globallibraries.pdf [1:18pm] fraz: sam: I like the global library approach, it's not too intrusive and can be ticked off. Do you mind updating the corresponding issue to reflect this? [1:18pm] sam: ok [1:18pm] fraz: many thanks
Sam Pullara added a comment - 06/Apr/05 04:19 PM[1:12pm] sam: fraz: all i think you should do with the plugin is make it easy to add it to their project using files already included with the plugin
[1:14pm] sam: fraz: right now you must download more than the plugin to run your groovy scripts
[1:16pm] fraz: sam: true, but should it be automatic or through a toggable option?
[1:16pm] sam: Fraz: i think it should show up as a global library you can click
[1:17pm] sam: can you add it to this list in IDEA? http://homepage.mac.com/spullara?/globallibraries.pdf[1:18pm] fraz: sam: I like the global library approach, it's not too intrusive and can be ticked off. Do you mind updating the corresponding issue to reflect this?
[1:18pm] sam: ok
[1:18pm] fraz: many thanks
What should be done if a given module (containing Groovy scripts) is already configured with a Groovy library older than the one shipped with the plug-in?