workspace

I have this problem when I queue a build. The build dies with the error The path C:\[Path]\Sources is already mapped in workspace [Server Name]. the same as this question . but I've removed all the workspaces on the build agent by running this command: tf workspaces /remove:* and also by deleting the TFS cache folder. I've also restarted the server, but the error keeps happening on each build. Glenn Slaven Ok, so the solution ended up being fairly similar to what YeahStu posted on here . I changed the Build Agent's working directory from $(Temp)\UI\$(BuildDefinitionPath) to $(Temp)\UI\$

The p4v Perforce GUI client has an 'Actions > Remove from Workspace' menu command which removes all files from the workspace that are under version control and were not opened for edit or delete. This functionality only seems to be available from the GUI client, I can't find any corresponding command in the ever growing list shown by p4 help commands . I thought of using p4 where , p4 files and some list filtering, but that doesn't seem trivial, so before I go about creating a script, does anyone have a better idea ? Specifying a revision of either #none or #0 will remove the files: p4 sync /

I am looking for the best practice of handling inter project dependencies between mixed project types where some of the projects are eclipse plug-in/OSGI bundle projects (an RCP application) and others are just plain old java projects (web services modules). Few of the eclipse plug-ins have dependencies on Java projects. My problem is that at least as far as I've looked, there is no way of cleanly expressing such a dependency in Eclipse PDE environment. I can have plug-in projects depend on other plug-in projects (via Import-Package or Require-Bundle manifest headers), but not of the plain

One of my workspaces in eclipse can't be opened anymore. The other workspaces work fine. How can I fix this? First I thought this is an eclipse problem, but since the other workspaces work fine, something must be wrong with the workspace. Try this-->>Goto .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi and remove workbench.xmi file to solve this issue: .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi. user7824731 I am using maven project with eclipse kepler ,I had also faced the same problem(workspace was not opening),please follow the below steps it may work (please

By workspace, I mean - I need to save the state of my open buffers (possibly in a user specified workspace file) and quickly switch to another set of open buffers, e.g. to continue working on files related to another project. Is there an Emacs plugin which allows this? Which one would you recommend? I use a combination of save-visited-files and workgroups . In fact, workgroups will probably do most of what you want by itself. My config: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; workgroups for windows (setq wg-prefix-key (kbd "C-c z") wg-no-confirm t wg-file

My Eclipse was getting slower and slower over time. Tips I found on the Internet did not help. What I did is completely deleted my workspace, created new one and reimported all my projects into the new workspace and this really made the difference. So my question is whether it's possible to perform this workspace clean-up without deleting and recreating workspace... Maybe there is some cache in workspace which is getting big? Any ideas? Thank you! Eclipse keeps track of all changes in local history. That might introduce slowdown over time. Local history is located at .metadata/.plugins/org

I have a couple of projects that I had started under Xcode 3.2.x some time ago. I switched to Xcode 4 a few days ago and want to make use of the Workspace feature as both projects. Basically, my plan is to extract some common features out of the two projects and make them a common library that both projects depend on. However, before I even get to the tricky bit of dependencies I get stuck just adding my two projects to the workspace. I tried creating a new workspace and selecting "Adding files to " from the context menu; I then select the .xcodeproj file from my first project and it appears