Could you build a minimal demo and post it to GitHub so we can take a look?

On 04.01.2016, at 19:08, Gabe Montero <gabemonter...@gmail.com> wrote:

> I have a plugin that defines a series of extensions to hudson.tasks.Builder 
> as well as an extension to hudson.scm.SCM.
> 
> In defining the config panel for each of these, a common field for each 
> leverages the booleanRadio tag with a default value
> and a field ref to one of the instance variables in either the Builder or SCM 
> extensions.
> 
> The default value shows ups for all the extensions to Builder, but does not 
> show up for the extension to SCM, even though
> I've added logging which confirms the getter for the field/instance variable 
> is getting called when the UI panel is rendered (which 
> I also took as a confirmation there is not a typo in the tag in the jelly 
> file).
> 
> Didn't see any references to a similar problem after searching.
> 
> Any hints or suggestions on how to debug down in the Jenkins layer?  Thoughts 
> on whether this warrants opening an issue against Jenkins?
> 
> thanks
> 
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/cfeeab88-16cb-432a-ac0c-dbd1881ea9ae%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/B3B98D49-17E1-4899-A0EC-4C71DA7C636D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to