Menu
▾
▴
#4 Improve deployment
Installation on the supported platforms should become far easier. Among the measures that need to be taken to achieve a 'forehead' installation, we may try to bring our 'own' libraries for serial i/o along. Users would not need to install serial i/o libraries before they can install JScan2052, if third party libraries could be brought along. RxTx should make that possible, if we can get the application to work with their libraries, and if licences allow.
Logged In: YES
user_id=1701854
Originator: NO
Robert,
The ant scripts are a great idea. I have only two small issues that you can help with.
First, the manifest file that is generated doesn't list the Main-Class (on my eclipse). This causes the jar distribution to not be "double clickable" to run it.
Second, I seem to have a brain cramp with getting the jscan2052logger.properties file in the right place. The modelservice.java file reads it in getLogger(), but it is throwing exceptions. I had this part working when the properties file was in the root of the project, but that isn't an acceptable place for it, so I stuck it in the same place as the others. Can you take a look at these two issues?
Logged In: YES
user_id=1727860
Originator: YES
Jim,
I thought I told you that the build.xml does not yet work. Sorry.
I was aware of the manifest file issue. I am just figuring some other things out related to the manifest file. (e.g. where to pull the rxtx libraries from.)
As to the logging-properties file: I saw in cvs you already figured it out. (Was a _case_ of _sensitivity_, not of the place, wasn't it?) I removed one of them, since my windows is confused. Tell me if your troubles remain.
Hold out, I'm working on the deployment issues. (They influence/prerequ all properties-file related things (and going with that the save preferences feature), and the "bring your own libraries" concept.)
Logged In: YES
user_id=1727860
Originator: YES
Corrected the build script.
Now does a complete build, including the rxtx libraries. Manifest file also included. Doubleclicking the jar file works on windows, please test on Mac, Jim.
The next improvement we need is to have some of the properties files inside the jar file and some outside (those who may be edited by the user or saved to by the application).
Finally we may add zipping the whole thing into a tgz file from the build into a deploy directory.
Logged In: YES
user_id=1701854
Originator: NO
Excellent. This works on Macintosh as well. I still have the comm.jar library in my build path, but only for debugging. Once we figure out the correct way to get around the deadlock problem with removeEventListener(), we can decide whether to drop javax.comm or include it in the deployed libraries via ANT.