Eclipse – JAR creation failed “Class files on classpath not found or not accessible for…”
Just do a clean and/or rebuild on the project. You can find it under the Project menu of Eclipse.
Just do a clean and/or rebuild on the project. You can find it under the Project menu of Eclipse.
You can try and export (as in “copy to another people workspace metadata directory”): </path/to/.metadata>\.plugins\org.eclipse.ui.workbench\workingsets.xml This is the file referencing your working sets. z0r adds in the comments: my team mate replaced his workingsets.xml with my version of the file, and it worked well. However, you must exit Eclipse before replacing the file, because Eclipse … Read more
EGit 3.5 and later In EGit 3.5 and later, there is a menu called Stashes in the Team context menu. It provides an action to stash changes and also lists any existing stashes. The same menu is also available as a toolbar icon and in the Git Repositories view: Selecting an existing stash from the … Read more
The two connectors should both work, here are the differences (more from experience by using them, not by reading their source code): SVN Kit: Works on all platforms, is a Java-only implementation (no need for DLLs or shared libraries). Is a little bit slower than JavaHL Native. Keeps its configuration at some other place than … Read more
Right click on Project1, then click on Properties. In the dialog that comes up, select Java Build Path, and then click on the Projects tab. There, add Project2 to the build path. If Project1 is a web app, you need to make sure your Deployment Assembly (same Properties UI) has Project2 there as well.
Click on the small triangle in the upper right corner of the problems view and select “Configure Contents”. In that dialog check “Show all items” and uncheck “Use item limits” to show all warnings.
Try running Eclipse as administrator, I just had the same issue and this worked for me.