Community
Participate
Working Groups
Build Identifier: eclipse.buildId=I20100608-0911 java.version=1.6.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -showLocation Command-line arguments: -os linux -ws gtk -arch x86_64 -showLocation AS IS: After upgrade to the 3.6 we see many new issues with target editor/update site editor on Linux. Actually target editor is now simply broken as it trows StackOverflowError's during: "Resolving Target Definition" in most cases. The difference to the "standard" Windows use case is that our Linux installation is owned by root and not writable, so that all extra plugins are installed under the different (/user.home/.eclipse_ide/com.verigy.ide_3.6_x86_64) location. The major pain with our case is, that even if I manage to avoid the StackOverflowError's, Eclipse/PDE doesn't seem to be able to grasp that the extra location is used for extra installed plugins, EVEN if this is extra specified in the target definition. So if now I open the update site editor, I can't see ANY feature installed into this the extra location. This was possible with the Eclipse 3.5. Reproducible: Always Steps to Reproduce: Install Eclipse as a root and use it as simple user on Linux. Specify the config area with -configuration @user.home/.eclipse_ide/com.verigy.ide_3.6_x86_64/configuration. AS user, install a lot of extra features to that Eclipse. Now try to create a target platform containing all the extra features installed before => resulting file is either not manageable with the target editor or the update site editor isn't able to see any extra features from the target. I will attach the stack trace/config data and example target files.
Created attachment 176205 [details] Example target files, config data, site.xml etc
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.