I would definitely suggest adding new portlets as new plugins. Then it's up to you to categorize them... In your case I see two different plugins, one for sonar, one for all the others. My idea would be to have all the portlets out of the main plugin (which then would contain only the infrastructure).
Marco On 12 December 2013 13:32, Georg Henzler <georg.henz...@googlemail.com>wrote: > I think we cannot add the sonar portlets to the sonar plugin, because that > would introduce the dependency to the dashboard plugin (this would mean > forcing all users of the sonar plugin to install the dashboard plugin). > > It would be an option to add the portlets to the dashboard view plugin - > on the other hand it probably gets at some point a bit monolistic if all > new portlets form the community end up in the dasboard view itself. > > @Peter & Marco: What do you think? > > Georg > > On Wednesday, December 11, 2013 11:16:57 PM UTC+11, Ullrich Hafner wrote: > >> Wouldn’t it make more sense to add your core portlets to the dashboard >> view plug-in and add your sonar portlets to the sonar plugin? >> >> Ull >> >> Am 11.12.2013 um 03:24 schrieb Georg Henzler <georg....@googlemail.com>: >> >> Hi all, >> >> I've created additional dashboard portlets to extend the >> https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View. They are >> very flexible (especially the Generic JS Portlet), but I have been using >> them mainly to create a Developer Dashboard that included the following >> information on one Jenkins page: >> >> * CI Build Status (obviously possible by default ;-)) >> * Latest SCM changes (using Recent Changes Portlet) >> * New Sonar Violations from last night's run (using the Sonar Portlets) >> * Server Status of DEV/TEST/INT (Deployment Job Status and current actual >> status using a Nagios-like URL for each server and the Generic JS Portlet >> to display the info) >> >> I believe nothing like this exists already (having checked >> https://wiki.jenkins-ci.org/display/JENKINS/Plugins) and I'd be happy to >> push it over to https://github.com/jenkinsci to make it available for >> everyone. >> >> For current source code and more information see >> https://github.com/ghenzler/jenkins-mashup-portlets >> >> Regards >> Georg >> >> >> -- >> 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 jenkinsci-de...@googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Marco Ambu E-mail: marco.a...@gmail.com LinkedIn profile: <http://www.linkedin.com/in/marcoambu> -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
