On Tue, May 27, 2014 at 6:56 PM, Kohsuke Kawaguchi <[email protected]> wrote: > the categorization comes after the plugin comes into being.
Really? Whenever I have created a plugin I have set a category in the wiki as just one of several routine tasks. > I'm all for allowing pluin authors to definitely describe excerpt, labels, > and so on. But I also don't really see why we have to bend over backward to > avoid hitting Confluence. For me that is a side benefit, but the real motivation is that I expect the official, signed update center JSON to be a simple function of the plugin artifacts that are fed into it from the Maven repository, without mysterious screen scraping of some wiki. If JENKINS-22926 is implemented and some extended columns in Plugin Manager want to show installation counts, ratings, etc. pulled from other databases or sites or astrological almanacks, that is fine. -- 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.
