Hello, I did the adaptation, and proposed it as a PR here: https://github.com/jenkins-infra/deprecated-usage-in-plugins/pull/8 I only handled direct dependencies, which is what is of interest for the developers I think.
I also fixed the javadoc links which were broken. As a consequence, I also wondered if there was something available to host plugins javadoc ? Arnaud Le jeudi 28 décembre 2017 00:17:05 UTC+1, Daniel Beck a écrit : > > > > On 26. Dec 2017, at 16:25, Arnaud Tamaillon <[email protected] > <javascript:>> 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/046c45b5-4d8f-40ab-8360-8e64c9a78662%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
