Your example highlights an issue: there is no reason to show `structs` to a user at all, since it offers no user-level features. It is just an API. No one chose to install it, they just got it as a dependency from some update of another plugin.
When I worked on NetBeans we could mark modules as being libraries (~ APIs) or bridges (integrations), which would get installed only as needed, and would normally be hidden from display. Perhaps Jenkins needs an equivalent. W.r.t. “bridges” I have an open RFE to deprecate optional dependencies in favor of these. -- 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/CANfRfr0haebpzEpyi%2Bp3%2BbEzvv0uYoEkFkW4wkH0ve6%2B_nf1xQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
