I see now that Jenkins is warning me about some old data. All of the places it's warning about have *plugin="[email protected]"*. I've been incrementing my version: 1.1.19... 1.1.20... all the way up to 1.1.33 now. All past increments have never been a problem, but suddenly this last one is?
If I manually edit the XML file and change it to * plugin="[email protected]"*, my config sections now show up. What does one need to do to keep data "fresh" as a plugin evolves? In this case, my data structures didn't even change, so it's not like I needed a readResolve(). On Wednesday, September 25, 2013 1:19:33 PM UTC-4, Brian Sayatovic wrote: > > I long ago developed a custom SCM plugin for SCM server, SourceGear Vault. > It had been working fine for years, with little tweaks here and there. > > Recently, I tried to make another tweak but found it so far out of line > with Maven, Jenkins, etc. dependencies that I had to up a lot of the > dependencies. But it built and deployed just fine and my jobs still build > as before. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
