On Fri, Sep 9, 2016 at 12:57 PM, Dan Jasek <[email protected]> wrote: > Anyone have a suggestion on what I am doing wrong?
Do not see anything obvious wrong. I would start by getting rid of Lombok here, as a likely source of risk. Or set a breakpoint in `AbstractStepImpl.prepareInjector`. > As the problem is in the magic of DI, I have hit a brick wall on where to go > from here. You are not obliged to use DI. Just extend `Step` and `StepDescriptor` directly, and your `Step.start` can call whatever constructor you like of the execution. You can still extend `AbstractSynchronousNonBlockingStepExecution` to pick up its background thread semantics; just call the `super` constructor taking `StepContext`. For context parameters, call `StepContext.get`, and list them in `getRequiredContext`. Really it is not much more code than the DI version, and a lot easier to understand and debug. Kohsuke is just enamored of Guice. :-/ -- 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/CANfRfr3pUQd%2BNcOo-vda6XecAt49XC5Zic9m%2Bhb44QUUNkVN7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
