Joe-E 2.1 released

Unheralded, late in the night, a new release of Joe-E has struck.  Check 
it out (unless you were watching the project page like a hawk and 
noticed the new version appear late Friday night).

Important notes:
- the plug-in ID (and corresponding nature and builder IDs) have changed 
to be more standard (it's now org.joe_e).  This doesn't have a direct 
effect on the UI, but it means that Eclipse thinks that this is a 
different plugin.  For this reason, I recommend that you disable the 
plugin in any existing projects (uncheck Enable Joe-E verifier) and then 
uninstall it before installing the new version.
Otherwise, some stuff will remain from the older version cluttering up 
the project metadata.

Sorry for the hassle; but it seemed to be the right thing to do, and I 
wanted to do it earlier rather than later.

- A package is now declared to be Joe-E code by the package annotation 
@org.joe_e.IsJoeE.  Yes, amazingly enough, packages in Java can have 
annotations; they are specified in a file called package-info.java in 
the package's directory.  The following one-liner declares the package 
pkg.name to be Joe-E:
@org.joe_e.IsJoeE package pkg.name;

You'll need to do this manually at present, but you can copy the 
package-info.java file between packages and it Eclipse will change the 
package specified by the file accordingly.

This means that there is no need to generate safej files for Joe-E code; 
the runtime allows reflective calls to all methods defined in Joe-E 
packages.  This change also makes it easier to use Joe-E for 
applications that span multiple projects, which used to require taming 
files for Joe-E code, but no longer do.

-Adrian