|Re: Problem with running CVS sources [message #783841 is a reply to message #783806]
||Thu, 26 January 2012 15:11
| Brian Svihovec
Registered: July 2009
The EUnit plug-ins are only required if you are planning to run the automated EGL language compliance tests for EDT. You probably don't need those right now, and you should be able to either delete these plug-ins, or ignore any errors in these projects when launching a runtime workspace. If you do want to run the EUnit test suite, you will need to add the BIRT extensions to your development workspace.
Regarding the widget issues, I have updated the WIKI page I mentioned above to include a better explanation of the problem and the solution. Even if you are not modifying code in the widget projects, you will still need to check out the latest version of these projects from CVS in your runtime workspace to avoid the compile errors that you are currently seeing. This is due to the fact that the version of the widget projects used by the New Project wizard come from the org.eclipse.edt.ide.ui.resources plug-in, which in your development workspace contains a version of the widget projects that were created a long time ago. To make things a bit more complicated, you can't replace the Dojo widget project (i.e. org.eclipse.edt.rui.dojo_0.7.0 or org.eclipse.edt.rui.dojo.remote_0.7.0) with the version of these projects stored in CVS, since the content for these projects is not updated in CVS either. Each of these Dojo projects is built from two additional projects, which are stored in CVS, and it is these two projects that you will need to check out from CVS.
Hopefully the WIKI now contains enough information for you to resolve the compile errors in your runtime workspace, but let me know if it does not and I can make updates as necessary.
Powered by FUDForum
. Page generated in 0.01707 seconds