Closed GoogleCodeExporter closed 9 years ago
Projects already using the current SBJSON can simply remove from the GData
project the parser version checked out by the library. So long as the newer
SBJSON is compiled into the same app, the library should work.
Original comment by grobb...@google.com
on 6 May 2011 at 9:14
But the interface is changed. Specifically, the SBJSON class is split into two
classes - SBJsonParser and SBJsonWriter. Without modification to GData code,
runtime error will occur.
Original comment by an0...@gmail.com
on 6 May 2011 at 9:30
I'll look into the practicality of moving to the newer version. Can a tagged
version be checked out from github with subversion?
Original comment by grobb...@google.com
on 6 May 2011 at 10:09
I've never done that. But this may be
helpful:https://github.com/blog/626-announcing-svn-support
Original comment by an0...@gmail.com
on 6 May 2011 at 10:52
From the comments there, it doesn't appear doable.
Original comment by grobb...@google.com
on 6 May 2011 at 10:53
I've updated the libraries to look for SBJsonParser/SBJsonWriter as well as for
the older SBJSON. The subversion repositories still pull in the older SBJSON,
but it should be easy now to remove that from the project and just use the
newer classes that are already compiled into the application.
http://code.google.com/p/gtm-oauth2/source/detail?r=28
http://code.google.com/p/gtm-http-fetcher/source/detail?r=42
Original comment by grobb...@google.com
on 10 May 2011 at 6:09
Thanks. Just tested, it works.
Original comment by an0...@gmail.com
on 11 May 2011 at 3:05
Original comment by grobb...@google.com
on 11 May 2011 at 3:20
Original issue reported on code.google.com by
an0...@gmail.com
on 6 May 2011 at 9:00