Re: Expose data of non-Jenkins library classes via remote API
On Fri, Jun 1, 2018 at 5:30 PM, Ullrich Hafner <[hidden email]> wrote:
> I want to expose data using the remote API for classes that I cannot change (or that should not depend on Jenkins), is there a way to expose these properties as well?
Subclassing is evil. Create new POJOs in your plugin which mirror the
relevant aspects of the external library and export whatever.