On Tuesday, May 27, 2014 6:50:07 PM UTC+2, Jesse Glick wrote: > > On Tue, May 27, 2014 at 12:13 PM, Stephen Connolly > <[email protected] <javascript:>> wrote: > > the classification needs to be editable after the fact of the release. > > Why? If you want to change it, just cut a new release, like you would > for the plugin display name or anything else. >
While I like the general idea of having a highly dynamic plug-in classification system based on tags in the wiki, there is another problem: The plug-in categories that are shown in the update center are hard-coded into the *messages*.properties* files in *core\src\main\resources\hudson\model* (e.g. "UpdateCenter.PluginCategory.builder=Build Tools"). When someone adds a new category-tag in the wiki, plug-ins still show up under "misc" in the update center. If the new category-tag gets added to Jenkins core eventually, only the following Jenkins releases show the new category. Everyone else still sees them under "misc". So I'd suggest to pull this out of Jenkins core, either into a plug-in or some infra module that generates the update center. Apart from that I'm in favor of self-contained plug-ins. There might be some meta-data (e.g. some kind of plug-in rating) that should be stored independently. At the very least as a fallback (if the plug-in does not provide a description, category, then use the one stored in the update center/wiki), because cutting new releases for 800+ plug-ins just to update the meta-data might be a bit tedious. -- 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]. For more options, visit https://groups.google.com/d/optout.
