As chance would have it I actually looked at this issue and the pull request just yesterday.
The actual code fix is pretty straightforward. It's the minimum required Jenkins version that makes me hesitate.
When I fixed the broken build I made sure not to increase the minimum required Jenkins version by too much. It's 1.625.3 right now and it seems fixing this will increase that number to 2.62. There's quite a few versions in between those two where people are using this plugin. Right now it seems like they are not updating the plugin anyway, but it might to too early to tell.
There's always the option of fixing this through reflection without increasing the required Jenkins version (as was done here), but that's complicated, ugly, hard to test, etc...
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.