On 11/06/17 17:42, Daniel Beck wrote: >> However, I still see some dependencies which seem bogus to me. > > All of those plugins implement features to support their use in > Pipeline, so have a dependency on them.
Thank you. Pipeline is dependent on them, or they are dependent on Pipeline? If the former, I should be able to delete Pipeline. If the latter, that is simply incoherent design (IMHO). I contend that, if I'm not using Pipeline, I shouldn't have to have any Pipeline plugins installed. I know that, in earlier installations, I had these plugins installed without any Pipeline plugins (which may not have existed then). If there are common features that are used by nearly all plugins, they should be extracted into a separate plugin or moved into Jenkins proper. The plugin world should not become like the Windoze DLL-hell. -- Dave Close, Thales InFlyt Experience, Irvine California USA. cell +1 949 394 2124, [email protected] "If your aren't in over your head, how do you know how tall you are?" -- T. S. Eliot -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/e91d7de6-8dee-e80c-eb7e-f1ff3f3e095b%40us.thalesgroup.com. For more options, visit https://groups.google.com/d/optout.
