Use official bob.jar release instead of bob-light.jar which is packaged in defoldsdk.zip

[JCash]

In order to simplify the defoldsdk.zip generation (speed, size is 500+mb!), we'd like to use the official bob.jar instead of the one packaged in defoldsdk.zip.
So, when downloading an sdk using a sha1, we should also download the bob.jar separately.

• The crux is finding out which sha1 to use for bob.jar.
• We also don't want to use a bob.jar that is older than the defoldsdk.zip (

The reason it's a crux is that the console sha1 doesn't have a matching bob.jar.
We always refer to the official one.
Will the latest stable one work?

After this step is done, we can remove bob-light.jar from defoldsdk.zip.

[ekharkunov]

According to my review I saw that bob-light.jar uses as a part of class path when Extender builds java code (usually plugins). As I understood we should have some of base java interfaces in class path to compile extensions to Bob's build pipeline.

Personally I prefer to pack everything related to build inside defoldsdk.zip instead of download and manage one more artifact.

I suggest:

1. At Bob's side create special annotation for classes like @DefoldExportable
2. Mark all needed interfaces with annotation.
3. After compilation collect all marked interfaces into small jar, for example, bob-pipeline-interfaces.jar
4. Pack new jar in defoldsdk instead of bob-light.jar
5. Update class path in build_input.yml with new jar.

New jar will be very small in terms of size.

If idea is ok for you - I'll processed and implement it.

[JCash]

As I mentioned offline, having clearly marked "public" api's is beneficial for us to maintain an document.
And also, for this defoldsdk, it should help when building plugins.