![]() Many times I've checked at that moment to see if the path to the shared folder is invalid, but it never is. If when I last had it open I was viewing files from those projects, the editor views just show errors, saying the files don't exist anymore. ![]() However, I've found that it's risky to bring down the Eclipse instance on the VM (not the "test instance", but the one that I imported the projects into), because quite often when I restart that Eclipse instance, the window comes up and shows zero projects. ![]() I connect to that instance from the Eclpse instance on the main CentOS box. I use a "shared folder" so I can access the host's files from the VM.įrom that Eclipse instance on the VM, I run an "Eclipse Application" launch config, with the "debug" VM parameters. In order to step through the code safely without locking up the machine (the app sometimes renders menus), I run an Ubuntu VM that also runs Eclipse, and I just import all of the projects (not copy) residing in the git repo on the main box. I have the code checked out in a git repo, and my Eclipse workspace references the projects defined there. I primarily work on an Eclipse plugin codebase. For quite a while now, I've been hampered with a very annoying problem in my development environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |