I've posted a possible alternative as a pull request to the git plugin.

The alternative tries to call the JGit 3 implementation.  If a 
NoSuchMethodError exception is raised, it uses reflection to find the close 
method (from JGit 4), and calls it (if it finds it).

Comments are welcomed on https://github.com/jenkinsci/git-plugin/pull/426

Mark Waite

On Wednesday, July 6, 2016 at 11:58:45 AM UTC-6, Mark Waite wrote:
>
> Will do.  My current goal is to investigate other ways of resolving the 
> issue without requiring that every plugin which depends on JGit must update 
> at the same time.
>
> For example, one of the experiments I hope to perform is to see if a 
> dependent plugin could catch the runtime exception due to the missing 
> release() method, and then use introspection to find and call the close() 
> method.
>
> I also have the goal to release git plugin 3.0 and git client plugin 2.0 
> before Jenkins World in September.  Beta testing has been positive, with 
> this JGit API change being the biggest hurdle detected to date.
>
> Mark Waite
>
> On Wednesday, July 6, 2016 at 7:43:56 AM UTC-6, Robert Sandell wrote:
>>
>> I have released Gerrit trigger 2.22.0-beta-1, thanks to a helpful 
>> contribution,  with the needed JGit 4 changes for users to try out.
>>
>> A helpful ping when Git Plugin 3 is released to main update center would 
>> be nice, so I can do the same.
>>
>> /B
>>
>> On Wed, Jun 22, 2016 at 7:43 PM, Jesse Glick <[email protected]> 
>> wrote:
>>
>>> On Tue, Jun 21, 2016 at 5:56 PM, Mark Waite <[email protected]> 
>>> wrote:
>>> > I could search the plugin tree for JGit references to see the
>>> > actual scope of the problem.
>>>
>>> I would start there, especially if you have a complete list of
>>> exhaustive members you could search for usages of.
>>>
>>> It would be very helpful if someone (hint hint Andres) were to
>>> routinely run `plugin-compat-tester` against all (@jenkinsci) trunk
>>> plugins with trunk dependencies, so we would at least find any
>>> regressions promptly. Also perhaps someone could resurrect Sorcerer
>>> and get it running on the @jenkinsci code base so we could quickly
>>> find method usages, even when they are of generic-sounding names like
>>> `release`.
>>>
>>> --
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24PiF6Lyp1VF75DpQgnreCWLvoRNdzv8YErw8cyOJWSA%40mail.gmail.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fe3829c8-0d74-4e19-8858-b3a1c0944b91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to