Community
Participate
Working Groups
Build Identifier: 20100917-0705 If i open a target definition file, its very unreliable as to weather or not it will actually get the components listed within it. Monitoring <workspace>/.metadata/.plugins/org.eclipse.pde.core the folder .bundle_pool is not always created and populated. This means that despite clicking 'Set as Target Platform' from the target definition editor, eclipse can't find the components within the defined target file. No errors are displayed, eclipse just refuses to recognise any of the components. Reproducible: Sometimes Steps to Reproduce: 1.Open previously defined target definition file in new clean workspace 2.Check if <workspace>/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool is created
This is likely related to how PDE uses p2 not p2 itself. Moving to PDE for consideration. Note that this area has been considerably reworked for 3.7. It would be interesting to hear what behaviour you see using a recent 3.7 build and the same target setup.
I did try 3.6.2 and also 3.7 M4. In 3.7 the target file wouldn't load at all. It all seemed completely broken, so i didn't get very far.
can you try 3.7M5 when it is done (later this week) and see. If you are still having trouble, then we'll need to see the .target file.
Yep i'll give that a go. Cheers
It would be helpful to see the target file to see if there is anything unusual about it.
Created attachment 188025 [details] Target file
Created attachment 188026 [details] problem 1
Created attachment 188027 [details] problem 2
I've just tried 3.7 M5 and have the same problem. 3.7 won't even load the target file. Instead you get warning items appearing or if you then close the target editor and reopen, errors. See the images. Removing individual units from the file and restarting eclipse, or removing entire locations simply moves the same errors into different locations. It doesn't seem to resolve at all. Perhaps i'm doing something stupid in the definition file?
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.
