Ditching some trailing eclipse warnings

I've managed to get to Inbox-Zero for warnings in the Debrief/ASSET eclipse build. It started at several thousand, and they had to be resolved individually - so it's no mean feat...

Mostly they've been associated with the introduction of Generics, the provision of synthetic accessors, and use of deprecated calls. The non-Java issues have been more thorny, however.

1. The plug-in's classpath library '.' does not have a corresponding source build entry. This build.properties problem is fixed by adding a Bundle-ClassPath: entry to the Manifest.MF file for that plugin. The bundle-classpath entry should just contain a single item: the name of the compiled Jar for that plugin.
   
2. An "source.libs/jcommon-0.7.1.jar" build entry is missing. This build.properties problem was caused becase there was an item in the Bundle-ClassPath entry that wasn't actually required (the jcommon lib). Deleting the unnecessary lib (to just leave that plugin's jar file in the entry) made the problem go away.
   

And that's all that was needed. I now have a warm feeling that it will be easy to keep on top of the warnings from now on.