Well, the reason that Ruby is "easy" is JRuby provides a lot of the interaction between Ruby and the JVM. There is IKVM that allows you to interact with Java libraries from .NET, but we would need something almost the opposite, a bridge between .NET and the JVM. Basically, Jenkins needs to be able to load .NET plugins as if they were Java plugins. The Ruby stuff has some helper stuff to take care of some of this bridge and make the Jenkins API more Riby-like. Do you know of something that could be used to provide the bridge I am talking about?
slide On Sat, Oct 27, 2012 at 7:59 PM, Andrew Gray <[email protected]>wrote: > Hi Alex, > > I proposed this for exactly the same reason :) > > How hard would it be to build on the great work already done with Ruby? > > Is there any reason why C# plugin support should not take the same > approach/architecture? > > What do you think? > > Anyone else? > > Cheers, > > Andrew > > > > On 28 October 2012 13:19, Alex Earl <[email protected]> wrote: > >> I've though about doing something like this, I would love it for the fact >> that I am much more of a C# dev than Java, so it would open things up a bit >> more for me. >> >> Slide >> >> Sent from my Windows Phone >> ------------------------------ >> From: Andrew Gray >> Sent: 10/27/2012 5:19 PM >> To: [email protected] >> Subject: C# plugins >> >> Hi All, >> >> What interest would there be in replicating the Ruby glue layer (enabling >> dev of plugins in Ruby) to C# (to enable development of plugins in C#? >> >> Cheers, >> >> Andrew >> > > -- Website: http://earl-of-code.com
