jSyncManager build process modified.

The jSyncManager team would like to alert developers using the CVS repository that the project JAR file build targets have changed.

In particular, building the "binjar" target no longer creates a JAR that contains all the jSyncManager project classes. Instead, it builds a JAR that no longer contains the API or jConduits.

The build the jConduits, there is a new "jconduitjar" target, which will put them into their own, seperate JAR file. To build the API, please use the existing "apijar" target.

This change has been made in order to alleviate some problems people were having with Java ClassLoaders when trying to use their own external jConduit and Transport plug-ins. Loading external plug-ins would fail in many cases, as the Classloader for their plug-in classes couldn't access the plug-in super classes if the jSyncManager was launched with the "-jar" option.

The main compile target to build the class files will still build everything -- this change only pertains to the building of the JAR files. If anyone has any questions, comments, or concerns about this change, please be sure to e-mail support@jsyncmanager.org.