...
New solution based on custom module location
In this case, we have to do some research related to following classes
Code Block | ||
---|---|---|
| ||
build/runner/Kepler.java build/project/ProjectLocator.java build/UpdatePresentTxt.java |
At the moment, Kepler looks for additional modules only inside ~/KeplerData/kepler.modules (and only in case there is a file "use.keplerdata" inside build-area). I would like to change Kepler such way it can take modules from arbitrary locations.
Handling locked DB file
We have to fix the issue here
Code Block |
---|
core/src/org/kepler/util/sql/HSQL.java The exception below originates in line 731 where the code calls DriverManager to open the connection to the db. We can try adding a new check for the database being locked and then use System.exit() to stop Kepler nicely instead of throwing exception. |
Create smaller Kepler release
At the moment we provide Kepler release with all the sources, class files, etc. This way, we require:
- lots of space (4 times more comparing to version without sources)
- lots of files to be copied/accessed (6 times more files - 60000 files when shipped with sources vs. 10000 files if we decide to ship stripped version)