Re: Eclipse vs plugin.jar

We're writing an applet. It does uses LiveConnect to talk to JavaScript
on the page. The classes for that - JSObject and friends - are in
plugin.jar, which can be found in the JRE lib directory.

We're developing using Eclipse. Eclipse has no idea about plugin.jar.

What's the right way to teach it?

We could put a copy of plugin.jar in our project. That's easy, but means
we're not using the installed version, which leaves us vulnerable to
version mismatch if Sun decides to make changes to this decade-old piece
of code.

We could add an external jar reference. That's also easy, and uses the
installed jar, but involves hardcoding the path to the JRE in the metadata.

We could use a classpath variable for the JRE's location, and add an
external JAR reference relative to that, which uses the installed jar
and doesn't hardcode the location, but it means everyone has to add a
new variable to their workspace (there isn't a predefined one for
JAVA_HOME or JRE_HOME, annoyingly).

We could define a 'library', which is some sort of bundle of jars, which
has the disadvantages of all the above approaches, and none of the
advantages.