Initial plugin setup needs to consider implied dependencies

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins.

      Assigning to Tom as he wrote the plugin wizard. CC kzantow

            Assignee:
            Keith Zantow
            Reporter:
            Daniel Beck
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: