[JENKINS-49217] Export ChannelTermination#cause when it is an ExportedBean · jenkinsci/jenkins#22545

2018-01-28T10:33:47.000Z

It is a follow-up to JENKINS-24452 . The behavior could be partially restored by checking the ExportedBean annotations on the field or by doing wrapping for non-exportable exceptions --- Originally reported by oleg_nenashev , imported from: Export ChannelTermination#cause when it is an ExportedBean assignee : minutehand status : Open priority : Minor component(s) : core label(s) : api, newbie-friendly, remoting resolution : Unresolved votes : 0 watchers : 1 imported : 2025-11-24 Raw content of original issue It is a follow-up to JENKINS-24452 . The behavior could be partially restored by checking the ExportedBean annotations on the field or by doing wrapping for non-exportable exceptions

(9 commenti) (0 reazioni) (0 assegnatari)Java (9474 fork)batch import

component:coreenhancementgood first issueimported-jira-issuepriority:minorresolution:unresolved

Metriche repository

Star: (25.266 star)
Metriche merge PR: (Merge medio 10g 9h) (93 PR mergiate in 30 g)

Descrizione

Guida contributor

Direzione di ricerca: Ispeziona la classe OfflineCause.ChannelTermination e il suo campo cause. Controlla se l'oggetto cause ha l'annotazione @ExportedBean. In caso contrario, avvolgilo in un wrapper esportabile o usa controlli instanceof per esportarlo condizionalmente. Testa con la suite di test esistente.
Tech stack: java
Dominio: backend
Tipo issue: Funzionalità
Difficoltà: 1
Tempo stimato: 1-3 ore
Stato attività: Attiva
Chiarezza: Chiara
Prerequisiti: Java
Adatta ai principianti: 80

Metriche repository

Descrizione

Guida contributor

Ricevi issue Easy fresche nella tua inbox.