I need to access Greenhopper classes from Groovy Runner.
Problem loading class: startup failed: /jira-plugins/ProductComponentSync.groovy: 17: unable to resolve class com.atlassian.greenhopper.model.issue.VersionWrapper @ line 17, column 1. import com.atlassian.greenhopper.model.issue.VersionWrapper ^ 1 error
Here is the correct link to code which solved my problem in custom event listener in Groovy Script Runner:
How to get Greenhopper Start and End date for Version object
As Jamie (the author of the Script Runner plugin, thanks Jamie :)) has commented, it's not particularly easy to do this, but you can do it.
Check out this other answers post with some sample Groovy code for getting the class from the plugin classloader, you can then instaniate the class.
The link didn't work for some reason, it is https://answers.atlassian.com/questions/73449/using-the-greenhopper-api-to-modify-rank?page=1#73622
Great answer though....
I am not GH API savvy. I might be using wrong approach to getting GH extension to Version object.
Here is another attempt. Still no luck though.
Last line returns null.
fails in what way? is GHversionService null?
GHversionService is not a component in the plugin.xml, so not sure if you can do getOSGiComponentInstanceOfType on it.
GHversionService is null despite getOSGiComponentInstanceOfType.
I can add a debug log after
to see if it was found
this code results in [LoggerService] Could not get instance of GHversionService
There is no straightforward way. You might be better off writing a new plugin and using component-import and bundle-instructions etc etc. The plugins 2 framework doesn't really allow for the possibility of optionally importing stuff to the classpath at runtime, at least I haven't found a good way to do it.
I recently enhanced the "copy project" function to clone the GH version hierarchy, scrum template, and other GH stuff, and elected to do it through http calls rather than the API. Seems to work fine although if you can use the public API that would be better.
The other way that should work is to modify atlassian-plugin.xml and add the imports you need to the bundle-instructions section, but this is not ideal as it would get overwritten when I update it.