Thanks Jeff, http://msdn.microsoft.com/en-us/library/system.runtime.serialization.json.datacontractjsonserializer.aspx is included in .Net 3.5 so it might not be ported to mono yet. I've been trying to use only 2.0 libraries since mono has really good coverage there. Looking a little deeper I think json.net will work. Thanks for the research!
J On Fri, May 7, 2010 at 2:44 AM, Jeff Hammerbacher <ham...@cloudera.com> wrote: > Hey Jeremy, > > I know nothing about C#/.NET, but some cursory Googling turned up > http://msdn.microsoft.com/en-us/library/system.runtime.serialization.json.datacontractjsonserializer.aspx, > which appears to be part of the standard library, and > http://james.newtonking.com/projects/json-net.aspx, which is MIT licensed > (compatible with APL). Do either of those work for you? > > Later, > Jeff > > On Fri, May 7, 2010 at 12:11 AM, Jeremy Custenborder < > jcustenbor...@gmail.com> wrote: > >> Boo on the LGPLv3. That means the patch I posted to jira is invalid. >> I'll refactor the json code to use another library. Heh this time I'll >> actually make sure that the library is compatible license wise before >> I start using it. >> >> On Fri, May 7, 2010 at 2:01 AM, Jeff Hammerbacher <ham...@cloudera.com> >> wrote: >> >> 1.) Excuse my ignorance but is LGPLv3 compatible with an apache license? >> >> >> > >> > Nope, sadly. >> > >> > >> >> 2.) Is JayRock a preferred library for json parsing? >> >> >> > >> > No idea, maybe ask Stack Overflow? >> > >> > >> >> 3.) Does anyone have issues if I bring in Apache Log4net >> >> (http://logging.apache.org/log4net/) ? >> >> >> > >> > Go for it! >> > >> >
