#6 Plugin Builder seems to corrupt projects

[Paulin]

I can't explain this one and at first I didn't think it was connected but then it started happening every time I use PB.

After performing a build, the plugin projects involved that are in my workspace all fail to compile (auto build on). They get 100s of errors which prior to the build they work fine. Looking at the Problem View the error appear to be related to not being able to find dependencies (AbstractUI can't be resolved).

I don't know what PB is doing when it performs a build and I can't even guess how it could be effecting the Auto Build of a project.

If you need me to try anything feel free to give me a buzz.

[Nobody/Anonymous]

Logged In: NO

I have had the same error happen multiple times. I could import the projects into a new workspace and they'd be fine for a few minutes, even after running a "Clean Workspace" command. But after running plug-in builder, my plug-ins were having difficulty finding plug-in dependencies which were set correctly.

[Nobody/Anonymous]

Logged In: NO

I also see the same problem with v0.4.0

[Markus Barchfeld]

Logged In: YES
user_id=646790
Originator: NO

Hi, thanks for the report. It seems to be a serious problem with 0.4.0 and I would like to fix it. I had encountered the same problem during the creation of the wink tutorial. Today I tried to reproduce the failure and I couldn't. Does anyone recall what produced the error?
I tried all the steps from the tutorial with no "success". Both in a runtime workspace and with pluginbuilder regularly installed. I have used Eclipse 3.3.1 with and withoud the deltapack, the subversion client was subclipse.
Is there a way to fix the corrupt workspace?

[Oliver Nölle]

Logged In: YES
user_id=379209
Originator: NO

Some further information:

- the very same problem was also present with the 0.3.0 version of pluginbuilder.
- restarting eclipse fixes the build problems in my case (but takes ages...)
- additionally to somehow corrupting the plugin dependencies (if you look into the java build path you see that there are no plugin dependencies listed) I also suspect the installation of the plugin (or invoking its "Generate build files") being responsible for causing a lot more build activity than necessary, ie. before starting a unit test, there are some parts of the workspace rebuilt although there haven't been any changes...
- I'm afraid the error is hard to reproduce, it does not happen everytime in my case, but maybe every 5th time (and not only on re-generating build files, but I can't remember what exactly the action was that caused the corruption)