Comment 1 for bug 205640

The fact that it is showing up as java would explain the behavior - I'm guessing that something was modified in the launching process for the newest Eclipse release. It is quite common to also see this type of problem with python apps (for example).

There should be some tools in place in the 0.6 milestone release to help alleviate these types of issues. Though they will not always be perfect... this is not intrinsically a bug in awn so much as it being inherently difficult to match up a launched process with a window. In this case what is probably happening is:

launcher spawns a process -> That process is a wrapper that spawns a 2nd process -> 2nd process opens the Elcipse window.

It proves difficult for awn to connect that 2nd process to the launcher.

The experimental standalone-launcher/taskmanager applet in awn-extras currently does have the necessary functionality to resolve this issue. Otherwise it probably won't be resolve before 0.6.