+1 to that. I would love to filter out plugins that aren't directly feature enabling. At the moment, we lack any sort of metadata to make that distinction, but I think that would help the site greatly. I think it would also be good to mark those OSS Jenkins is recommends during the install process to filter in or out.
...but that doesn't change the fact of the math, though, as far as the charts go. On Thursday, September 1, 2016 at 4:01:35 AM UTC-7, Jesse Glick wrote: > > 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/dc0544c6-712b-4bc2-b426-b4e66fd5f192%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
