+1 on Daniel's point. This appears to be unmaintained but is a very useful plugin.
I've only used it on the job dsl plugin, but have done Gradle work before outside of that. I'd be happy to look through the pull requests and whatnot. I can't claim blazing fast response speed but can definitely lend a hand on that plugin. On Monday, August 18, 2014 3:22:04 PM UTC-4, Daniel Spilker wrote: > > Hi, > > I have been using the Gradle JPI plugin to build the Job DSL plugin for > some time now. It has been doing great so far, but it also has it's issues. > The biggest issue is that it seems to be unmaintained. > > Every time I hit an issue with the Gradle JPI plugin, I'm close to porting > the Job DSL plugin to Maven. But the Job DSL plugin is written in Groovy > and I like the idea of having a full Groovy development stack and IMHO the > Groovy integration in Gradle is much better than the available Maven > plugins. > > I'm not a Gradle expert (yet), but I could volunteer to do some work. I > already reported a few issues and opened several pull requests. Apart from > that, I would like to get the plugin migrated to Gradle 2.0 and get rid of > all the warnings it produces in the build output. > > Is anyone else using the Gradle JPI Plugin? Should we just scrap it or > should we try to find a new maintainer? > > Daniel > -- 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.
