Problem with External Plug-in Libraries

[pavolzbell]

After clicking on Update version... I get the following error:

Cannot display current project version state.
Project does not exist: C:\workspace\project\External Plug-in Libraries

[b8]

It seems that you've a selection with a project that doesn't exist anymore. Do you also get the same error after refreshing the entire workspace?
There should be a stack trace in the Eclipse error log. Please provide it so that I can give you more hints.
Anyhow, the exception is ugly and we should do a nice error handling!

[pavolzbell]

I tried to refresh whole workspace, but it did not help and double-checked that all projects exist. Unfortunately there is nothing in the Eclipse error log (checked both view and log file on disk). If you do not have any clue what the problem is, I could try to compile and debug the plugin from sources.

[b8]

Hmm strange that this is not getting logged.
Maybe there is a problem with the spaces in the file path.

[pavolzbell]

Well that could be it. But the problem is that the non-existing project is sort of meta - I mean, External Plug-in Dependencies or Maven dependencies or JRE System Library is not really a project - just a link to referenced jars. I will try to be more clear, so In package explorer it looks like:

- com.example.one
-- .settings
-- .classpath
-- .project
-- pom.xml
-- build.properties
-- src
-- META-INF
-- JRE System Library [JavaSE-1.7]
-- Plug-in Dependencies

when I right-click on com.example.one and select Update version... it fails with:

Cannot display current project version state.
Project does not exist: C:\workspace\project\External Plug-in Libraries

[b8]

Well, when the dialog opens it examines the entire universe. By default, the universe is based on all projects in the workspace. We only traverse file directories, no virtual folders.
It is possible that you select com.example.one but the error is in another project in the workspace. Either you add a project root in a universe which points to the "external plug-in libs" (when you're using a .universe file) or one of your workspace projects is effectively containing such a folder in the file system (?).

[pavolzbell]

well, I checked Eclipse workspace metadata and found traces of the External Plug-in Libraries project which was probably created by mistake some time ago. I tried to fix the workspace but eventually had to wipe it out completely and import projects from scratch again. After this workspace reset the plugin works. Thank you for your help.

I leave the issue from now on to you, as I think that in such case your plugin should ignore such malformed (unreadable) projects or at least show better error message and leave sufficient info in Eclipse error log

[b8]

Okay. Yes, we have to improve error logs and white space handling in file names.