| [cross-project-issues-dev] org.eclipse.pde.junit.runtime and org.eclipse.jdt.junit4.runtime not found |
|
Hi An old problem seems to have reappeared since the double restart of slave1 at the weekend One or other of org.eclipse.pde.junit.runtime or org.eclipse.jdt.junit4.runtime may be reported not found during JUnit tests. Workaround: Add dependencies to org.eclipse.pde.junit.runtime and org.eclipse.jdt.junit4.runtime from some undistributed plugin such as a tests plugin. Regards Ed Willink -------- Original Message --------
Hi Ed, Adolfo, This might be the same as we see with Acceleo : http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06420.html . Our builds failed (and still do) on some of the slave with cryptic errors of "*junit* not found", often with pde or jdt namespaces. We had to tie our builds to slave1/slave6 to make them work... might be something to try in your case too. Laurent Goubet Obeo On 20/08/2012 17:47, Ed Willink wrote: > Hi Adolfo > >> The branch tests build has suddenly started to fail because >> org.eclipse.jdt.junit.runtime is not in the workspace; it isn't and >> never was and isn't in the plug-in requirements. Perhaps JDT/JUnit >> support has suddenly exposed an assumption. > Just did a QVTo build and org.eclipse.jdt.junit.runtime was loaded > into the workspace. But it bombs on org.eclipse.pde.junit.runtime > instead. > > Regards > > Ed Willink > _______________________________________________ > mdt-ocl.dev mailing list > mdt-ocl.dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev > |
_______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2197 / Virus Database: 2437/5212 - Release Date: 08/20/12