Currently, the way we package the JPPF jars and the dependencies for the JPPF components is a mess. For instance:

• jppf-common-node is a dependency for all components, even those that do not need the node code. It also contains all the utility classes that could/should be in a separate module and/or jar file.
• jppf-common contains client-side package names
• jppf-server contains node-side code along with the server-side code
• some package names can be found in multiple modules, that's messy
• a large part of jppf-admin contains code that should be reorganized as a separate library, with more meaningful names (i.e. the "Options" APIs to generate Swing components from XML documents)

What we propose is to reorganize the packaging, and possibly the SCM repository to achieve something more consistent, easier to build and to install.