You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <pl...@hi5.com> on 2008/05/01 12:26:40 UTC

Re: Json-lib instead of json.org

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" <be...@google.com> wrote:

> On Mon, Apr 28, 2008 at 6:04 PM, Paul Lindner <pl...@hi5.com> 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.)


RE: Json-lib instead of json.org

Posted by Nick Lothian <nl...@educationau.edu.au>.
If you use this method, can you please namespace it (ie, import it into org.apache.shindig.org.json) so it doesn't clash with other projects which have had to do the same thing (eg, my project)

Although theoretically it shouldn't matter I suppose...

Nick

-----Original Message-----
From: Kevin Brown [mailto:etnu@google.com]
Sent: Friday, 2 May 2008 2:09 AM
To: shindig-dev@incubator.apache.org
Subject: Re: Json-lib instead of json.org

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 <pl...@hi5.com> 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" <be...@google.com> wrote:
>
> > On Mon, Apr 28, 2008 at 6:04 PM, Paul Lindner <pl...@hi5.com> 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.)
>
>

IMPORTANT: This e-mail, including any attachments, may contain private or confidential information. If you think you may not be the intended recipient, or if you have received this e-mail in error, please contact the sender immediately and delete all copies of this e-mail. If you are not the intended recipient, you must not reproduce any part of this e-mail or disclose its contents to any other party. This email represents the views of the individual sender, which do not necessarily reflect those of education.au limited except where the sender expressly states otherwise. It is your responsibility to scan this email and any files transmitted with it for viruses or any other defects. education.au limited will not be liable for any loss, damage or consequence caused directly or indirectly by this email.

Re: Json-lib instead of json.org

Posted by Kevin Brown <et...@google.com>.
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 <pl...@hi5.com> 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" <be...@google.com> wrote:
>
> > On Mon, Apr 28, 2008 at 6:04 PM, Paul Lindner <pl...@hi5.com> 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.)
>
>