Hi Stéphane,
This error is there because one of the Ceylon module archives required by the Ceylon IDE plugin, and provided by proxy projects, is not there. In this case it seems to be the
ceylon.file module.
This can happen in the following scenario :
1. You have the
ceylon-sdk project opened
in your main Eclipse
2. You have all required-bundle-proxies/* projects opened
in your main Eclipse
3. You have the Ceylon IDE plugin installed
in your main Eclipse (for example from the dev update site)
4. You start the Ceylon IDE plugin to test it
through 'Run as Eclipse Application'
5.
In your main Eclipse you do some action that will triggger the build of your workspace, and also the build of your
ceylon-sdk project :
- this will remove all the SDK generated archives from the 'modules' Ceylon output directory
- The proxy projects related to the required SDK modules (ceylon.file, ceylon.collection, ceylon.interop.java) have a link to these archives. And since they have been deleted by the workspace build, they might need to be refreshed in order to be available again.
- If you don't do this refresh, the linked car will not be seen anymore, and you will get those errors when trying to resolve packages from these archives.
The main point is that, with this build scheme (bundle proxys projects), the Ceylon IDE plugin that is
'run as Eclipse Application' is finally pointing directly to the archives in the Ceylon output directory of the
ceylon-sdk or
ceylon.formatter. So if you have those 2 projects opened
in your main Eclipse, as soon as you trigger a workspace build that involves the clean of the
sdk or
formatter, you might encounter such errors in the Ceylon IDE plugin that is
'run as Eclipse Application'.
I'll change the destination of the link in the proxy-projects related to the sdk or formatter in order to point to the jars in the generated OSGI repo. This is *not* deleted during clean builds.
If this help removing this weird use case , I'll push the change and let you know.
David.