Currently, when the plugin is built, the development workspace build process puts both the regular and _g (debugable) version of the plugin so (libjavaplugin*) in the same directory.

This is actually inaproriate. We need to have a policy of no more then one file in the subdirectory. This is due to the fact that some installation schemes take path and treat evey file it sees as a plugin.

This would result in the container trying to use both the debug and non-debug version at the same time.

This is typically not a problem in release becuase the kitting process excludes the _g version.