> On 26. Dec 2017, at 16:25, Arnaud Tamaillon <[email protected]> wrote: > > This would help manage the life cycle of deprecated symbols by providing a > tool to plugin authors to check dependent plugins for breaking changes. >
http://updates.jenkins-ci.org/update-center.actual.json is the raw JSON with dependency information, but note transitive dependencies may be a problem. To get actual API usage, you can adapt https://github.com/jenkins-infra/deprecated-usage-in-plugins fairly easily to look for specific signatures or classes. Just rip out most of DeprecatedApi and replace with a fixed list of signatures; or even just check for a className.startsWith("my/package/name/" in DeprecatedUsage. -- 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/67CA81ED-EBB2-47B0-B379-F3CD15F956FF%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
