classpath issue in launchconfiguration of eclipse

[niels]

I worte a plugin and started the application with the launch-configuration of eclipse.
I struggled because my plugin was loaded twice. The reason was, that
the file play.plugins founded in the source-folder of my module and a
copied version in "eclipse/classes/play.plugins". The solution is to
set in the Preferences -> Java -> Compiler -> Building "filtered
resources" to "*.launch, play.plugins". Ok this could be easily added
to documentation. Not so easy to eclipsify.

But after thinking little bit about the constellation I get a couple
of question?
1. Could I get trouble with the compiled classes, because they are not
enhanced? Then the eclipsify command should change. Or will the
classes enhanced while loading them? I don't analyse the code in
ApplicationClassloader in detail.

2. Why was the plugin loaded twice? Is there a useful scenario or
should be a filter to make this impossible?
See http://groups.google.com/group/play-framework/browse_thread/thread/4d9ee878b97b2d70#