Community
Participate
Working Groups
Was performing the 'Interdependency Tests' testcase found here: http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E/vep-home/WebContent/docs/testcases/interdependency/interdependency.htm Basically Project1 had JFrame, Project 2 had JPanel. The JFrame has contentpane set to the JPanel in Project2. A compiler problem was induced into the JPanel class (added import foo.bar;) and the class saved. Going to the JFrame shows the error in the contentpane. Now go back to Panel and remove the erroneous import and save the file. Going back to the JFrame doesnt fix the problem.
Removing target. This can't be contained for 1.0.2 because it is too big. The problem is that for us to know that we need to recycle the VM, we need to know that we are referencing that class. The way we do it now is that we see if the vm proxy registry has referenced that class. The problem here is that once it goes bad, though it looks good in the code (i.e. there are no compile errors in the JFrame), it never succesfully instantiates so we can't get a reference to it in the proxy registry. Since it is now not in the registry we don't know that it is now good and of interest.
*** Bug 78940 has been marked as a duplicate of this bug. ***
