Community
Participate
Working Groups
N20050608-0010 I have auto-build on. Until this week I could 0. have dev workspace without compile errors 1. get a new drop 2. import existing unshared plug-ins as binary projects (not linked) ==> auto-build is started and at the end my workspace has no compile errors This is no longer the case importing N20050608-0010 with N20050608-0010: the build starts but it is not capable of incrementally build my workspace. Errors remain saying "The project A cannot be built its prerequisite B is built." for most of the projects. - importing a second time does not fix the problem - the projects are imported correctly: clean and full build fixes the problem Marking as 'major' since it turns a completely fine workspace in one full of errors and requires me to do a full build.
when autobuild is on, PDE imports the projects into the workspace and that's it. PDE is totally out of the picture after that. Resource notifications and the java builder take care of the rest. Whether a build is needed and/or what kind of build is needed is totally up to the compiler.
Cannot reproduce with N20050608-0010 + JDT/Core HEAD. I had two plugins from CVS jdt.core and jdt.ui ones. I first import other required plugins and build finished normally without any error. Then I import all other plugins and, again, build finished fine... Can you make a second try tomorrow with N20050609-0010 build (if usable)? Thx
mmh, maybe I misunderstood your steps but to me it looks like you performed a completely different test case: you imported plug-ins that did not yet exist in your workspace while I had all those plug-ins already and I re-imported them. - did you import the required plug-ins as binary projects (not linked)? - I have disabled all external plug-ins on the PDE Target platform pref page - I'm just re-importing right now...
What might also be important: after the first full import of the required plug-ins shut down and restart. Then import the existing binary projects (not linked) again.
Re-importing once imported build X and running on X seems not to reproduce the problem. I'll let you know tomorrow morning what happened when I started with N20050609-0010 and import N20050609-0010.
Imported using N20050609-0010 and it worked. The difference to when I reported this bug is that I waited several minutes until the jobs view calmed down before importing. Whenever I switch to a new version my workspace seems to do a (full?) build. I was probably importing while there were still some build and/or other init jobs running.
You're right. When I did my test, plugins I imported didn't exist in my workspace. So, I redo some tests this morning using build N20050609-0010. In my workspace, I initially had jdt.core and jdt.ui plugins loaded. I performed several imports for all required plugins (40) of these jdt plugins. Here are these imports: 1) Binary projects with linked contents 2) Binary projects 3) Projects with source folders 4) Binary projects Of course I had set auto-build on before and if import 1) didn't override existing plugins as they were not in my initial workspace, imports 2), 3) and 4) are obviously re-import and look like your initial test scenario (although it was not really obvious that it was a re-import... ;-)). Then, I never get any problem at the end of auto-build, even if I didn't have wait long time between each re-import. So, I think we agree to close this as WORKSFORME PS: The auto-build is due to new build state version number (see What's New section in our buildnotes_jdt-core.html): ... <li>The build state version number has changed. A full build of all projects in the workspace will be triggered upon startup if autobuild is on, or on the next build if autobuild is off.</li> ...
To verify I just ran a similar scenario again without problems.
