On Wed, Apr 22, 2015 at 4:14 AM, <[email protected]> wrote: > While debugging, at AbstractItem.java:324, I got to see that the parent was > null (after Jenkins restart). > > I am not sure what is wrong and what I am missing.
Your SpecialMainProject or its children is somehow to blame, not the Jelly views. Most likely your mistake was persisting its children in the `children` field. This cannot work. Creating a new project type is a serious endeavour; there are a lot of subtle considerations, and you have to understand the details of how Jenkins loads and save items. I would not attempt it unless you are pretty experienced with plugin development. It is usually not something you want to do even then; generally you want to tack behavior on to an existing project type. -- 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/CANfRfr2V6bw2b_BvxxBn%3DbF_Eoa0gQSxcc0%2BAS%3DAte02u24MwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
