If we don't move to the other json lib, we could always just import the json.org code into shindig directly. I've seen other projects doing this. I find it unlikely that json.org itself will ever host an SCM repo, but they might let someone else take over maintenance of the project if asked.
On Thu, May 1, 2008 at 3:26 AM, Paul Lindner <[EMAIL PROTECTED]> wrote: > It appears that the latest code from json.org fixes this bug. I built a > new > json.jar and dropped that into my internal build and all is fine. > > Shindig builds with some maven snapshot from late 2007. Sadly it appears > that this code could use a good source code control system. I'm relying > on > zip file timestamps to figure out what's been updated, and when. > > Any chance someone can update the maven repo with current code? > > > On 4/29/08 11:06 AM, "Brian Eaton" <[EMAIL PROTECTED]> wrote: > > > On Mon, Apr 28, 2008 at 6:04 PM, Paul Lindner <[EMAIL PROTECTED]> wrote: > >> What do people think about switching over to json-lib > >> (http://json-lib.sourceforge.net/) instead? It appears that this is > already > >> used by Abdera and some other Apache projects. > > > > Any chance of us contributing fixes back to json.org? You've already > > proved that you can fix json.org code, and we don''t know that the > > json-lib code will be better quality. (Both are used inside google, > > but json.org more widely than json-lib.) > >
