Distributable without org.json

[Miguel Alvarado]

Wondering why org.son is baked into the jabsorb distributable, why not
keep it as an external dependency? Is there a distributable that does
not include org.json?

Miguel

[Arthur Blake]

A couple of reasons.

1. There is no org.json jar distributable that I know of so if we were
going to do that we'd have to build a separate org.json jar file as
part of the jabsorb build process... (org.json is only distributed as
source code as far as I know.)

2. org.json is central to jabsorb and jabsorb can't live without it so
it's simpler to just bake it in and not worry about someone trying to
mix and match a different version of it rather than the one that we
have tested carefully and that passes all the unit tests. (Also there
is no externally exposed version control for org.json , so it's hard
to track changes and updates to that project.)

It might make sense to refactor the package names for org.json inside
jabsorb and we were doing that at one point because of needed
customizations to the org.json library. I was able to get the needed
customizations accepted into the main org.json library and so we
didn't have to do that anymore.

On Apr 15, 5:26 pm, Miguel Alvarado <miguela.a.alvar...@gmail.com>
wrote: