Community
Participate
Working Groups
To reproduce: 1. Create a folder within an existing PDE project. 2. Create a build.properties file within that folder. 3. Open the file. The editor will open the build.properties file for the project as a whole. (And to the wrong page, so this is tangentially related to bug 318657.)
This works for me using 3.6. I added a /test/build.properties to the project. Was able to open/edit the files with the build.properites editor independently.
Darin, On reconstructing a test case from scratch I discovered that this only happens in some circumstances -- that wasn't obvious because I had many projects open at the time and I assumed that it was a more general issue. Here's a test case that I ran through from scratch. It might fail in other circumstances but I'm certain that it fails in this one for me. 1. Create a new *Feature* Project. 2. Create a folder "test" within that project. 3. Create a file "build.properties" in test. 4. Open the MANIFEST.MF file for the feature, i.e. test.feature/MANIFEST.MF. 5. (At this point, you might move to the build.properties page.) 6. Open the build.properties file in the test folder, i.e. test.feature/test/build.properties Note that if you simply open build.properties this own't happen, because that causes the simpler build editor to open. I'm on Mac OS X (changed to specify) so if you can't reproduce on your platform it should be tested there.
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.
