Hello all, I'm about to finish a plugin to build Play!Framework projects from Jenkins.
There is already an available implementation from Takafumi Ikeda that hasn't been maintained since some 3 years ago. Play!Framework changed a lot since then and Jenkins have grown up a lot as well. In summary, the plugin doesn't seem to work anymore (at least I didn't manage to make it work without repairing some source code). It uses some deprecated methods as well. https://github.com/jenkinsci/play-plugin Then, I decided to create a plugin from scratch. It's simpler in terms of implementation, but with a better interface (imo) and structure. I plan to contact the Play!Framework community soon to get some better use cases and see how I could improve it a bit more... Anyway, my question here is: *should I release it to jenkins as a new plugin or should I contact the play-plugin developer and see if I could overwrite it?* >From one hand, it's a complete new code, new project, which could characterise it as a new plugin. On the other hand, it provides more o less the functionality of the existing plugin, which is no longer supported and, afaik, broken. (I can be wrong here, ok?) So, the next step depends pretty much on the policy of the Jenkins community regarding plugin release. Cheers, Rafael -- 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/d/optout.
