About cross-platform JDIC.
In order to provide a cross-platform release, we have 2 reasonable choices.
One is to rename some classes that have an identical name on different platform. Then bundle all classes into one jdic.jar.
The other choice is to separate the jdic.jar into 2 jar files, named jdic.jar and jdic_stub.jar. The jdic.jar will contains all shared classes and jdic_stub.jar contains classes for specified platform. In this way, we will have several jdic_stub.jar each for a certain platform. They will be placed in separated sub-directory. So, in order to use this cross-platform jdic, we have to modify the classpath at runtime depends on the runtime platform. Of course, this can be done by using customed Classloader. But, obviousely, that will make things more complexity.
Since JDIC is targeting to be integrated into JDK. If so, there will be no problem with cross-platform.
Eventually, JDIC team decided NOT to provide a cross-platform release.
Since i have promised to offer a cross-platform release previously, i try to provide a useable cross-platform jdic binary. It use some reflect mechanism to deal with the class loading problem. It is not a good way to do that. If your application use your own classloader which is not extends from java.net.URLClassloader, there will be a problem of using this cross-platform jdic.
You can get it at:
This is a cross-platform jdic BUILD. It dosen't contains Packager. NOTE: IT IS NOT A JDIC RELEASE! AND IT MAY NOT STABLE! WE DO NOT RECOMMEND YOU TO USE THIS BUILD.
And i may not provide a cross-platform build in the future. If you realy want it, you can modify jdic code, and build it by yourself.