Should our code generator be part of tightdb.jar?

[kspangsege]

In my opinion, the code generator should not be part of tightdb.jar, because it is only needed during compilation of the customers Java code. When the customer deploys the code, they still need to include tightdb.jar, but there is no longer any need for the generator.

I suggest we produce two JARs:
tightdb.jar
tightdb-codegen.jar

[bmunkholm]

How much code do we save?
It will also be more "difficult" to handle/understand the two jar's.
Hmm---

[nmihajlovski]

I re-configured the JAR plugin to package only the "com.tightdb" and "com.tightdb.lib" packages into tightdb.jar. And tightdb-devkit.jar remains the same, so it contains the code generator classes etc.