bridge-method-injector 1.21 
<https://github.com/infradna/bridge-method-injector/releases/tag/bridge-method-injector-parent-1.21>
 
has been released.

On Tuesday, May 11, 2021 at 12:34:27 PM UTC+1 [email protected] wrote:

> https://issues.jenkins.io/browse/JENKINS-65605 for tracking purposes.
>
> KK has been pinged to see if someone can get access, (even if just to 
> approve a transfer request).
>
> /James
>
> On Tuesday, May 11, 2021 at 11:05:58 AM UTC+1 [email protected] wrote:
>
>> The bridge method injector project looks abandoned? We may need to fork 
>> it to release a fix 
>>
>> On Tue, 11 May 2021 at 11:00, [email protected] <[email protected]> 
>> wrote:
>>
>>> There are 2 regressions that I know of currently in 2.288,  one is a 
>>> blocker and the other possibly so.
>>>
>>> 1. the `WithBridgeMethods` annotation no longer works and so we would 
>>> break compatibility with plugins using bridge methods from core  PR to fix 
>>> the injector is 
>>> https://github.com/infradna/bridge-method-injector/pull/25 and this 
>>> will need a release and a Jenkins PR and then backporting. (will create a 
>>> Jira soon)
>>>
>>> 2. the HTML form submission has broken quite a few tests (could be 
>>> HTMLUnit bug, or other but there are a number of plugins now with failing 
>>> tests when bumping to this core) 
>>> -> https://issues.jenkins.io/browse/JENKINS-65585  , 
>>> https://github.com/jenkinsci/jenkins/pull/5405#issuecomment-836265920 
>>> and https://github.com/jenkinsci/jenkins/pull/5479
>>>
>>>
>>> /James
>>>
>>> On Monday, May 10, 2021 at 3:55:22 PM UTC+1 Oleg Nenashev wrote:
>>>
>>>> Then let's postpone it until .2 at least
>>>>
>>>> On Mon, May 10, 2021 at 4:44 PM Basil Crow <[email protected]> wrote:
>>>>
>>>>> On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev <[email protected]> 
>>>>> wrote:
>>>>> >
>>>>> > I wonder whether we should also create a Remoting 4.8 backport this 
>>>>> time: https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
>>>>> > There are 2 bugfixes which seem important though we could also just 
>>>>> embed 4.8 into the LTS line. THere is one performance RFE and one minor 
>>>>> feature added, so just backporting the version looks safe enough
>>>>>
>>>>> #449 is off-by-default and anyway only applies to the Swarm client
>>>>> rather than the Jenkins controller. The other changes, while not
>>>>> regression fixes, seem safe to me. I don't feel strongly either way.
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to a topic in the 
>>>>> Google Groups "Jenkins Developers" group.
>>>>> To unsubscribe from this topic, visit 
>>>>> https://groups.google.com/d/topic/jenkinsci-dev/TPQum9wHFVg/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%40mail.gmail.com
>>>>> .
>>>>>
>>>> -- 
>>>
>> 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/c1032e1c-b60b-4780-8d9e-a4fd116f9c36n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/c1032e1c-b60b-4780-8d9e-a4fd116f9c36n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/d24d1e9e-b315-427b-89d9-1d86a970d621n%40googlegroups.com.

Reply via email to