Community
Participate
Working Groups
Build Identifier: I20110526-1708 it seems to be the same as bug346052 - which is somehow classified as "normal" - but this breaks existing projects and imo is a blocker. Reproducible: Always
Are you saying that the fix for 346052 is causing your existing projects to break? Can you be more specific, for instance, can you give more details about what variables you have setup, and how they break your linked resources resolution? Although it's true that the fix indeed changes the way path variables are resolved, the only variables affected are the ones that were resolving incorrectly to an empty strings. So unless your project was relying on a bug for resolving variables to empty strings, it shouldn't affect backward compatibility.
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. -- The automated Eclipse Genie.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
