Community
Participate
Working Groups
Build Identifier: 20100603-0907 From a fresh installation of HeliosRC3. Once I go to Preferences:Plug-in development:Target Platform:Running Platform: edit. In the Locations tab: Problems occurred getting the plug-ins in this container Notice that this bug seems to be regressive. I have already installed HelioRC2 and the platform activates correctly. Reproducible: Always Steps to Reproduce: 1.Installation 2.Preferences:Plug-in development:Target Platform:Running Platform: edit.Locations tab: 3.Problems occurred getting the plugins in this container 4.list of plugi-ins:ch.qos.logback.classic_0.9.19.v2010.05.19-1505 5.At this point in the Error log view: Http error retreiving service message 6.
Can you attach/describe the target being edited?
Created attachment 171266 [details] Preferences down to Target platform
Created attachment 171269 [details] Edit the Target platform
Could you attach one of the problematic plug-ins or point us to where we could get the version you are using? (i.e. ch.qos.*, javax.mail.glassfigh, etc.).
Created attachment 171393 [details] plugins missing in eclipse/plugins directory
Created attachment 171394 [details] Error when Running Platform (active) is clicked just before clicking on the Edit bottom
The last issue you attached is a parsing exception from Mylyn as is likely unrelated to your target platform problem. Can you please point us to where we can download the plug-ins that have errors. They are not part of the SDK and they do not come as part of Mylyn. What else do you have installed?
(In reply to comment #7) > The last issue you attached is a parsing exception from Mylyn as is likely > unrelated to your target platform problem. Can you please point us to where we > can download the plug-ins that have errors. They are not part of the SDK and > they do not come as part of Mylyn. What else do you have installed? I'm puzzled here. I haven't installed nothing else. Maybe imported preferences but I would say no either. This is what I did. I went to "|http://www.eclipse.org/downloads/packages/release/helios/rc2" and download "eclipse-rcp-helios-RC3-win32.zip" unzip in my hard drive open eclipse check preferences
I downloaded the linux RCP/RAP build from the link you provided and it contains 426 plug-ins which all appear correctly in my target platform. I can run the Eclipse and view the target and I can also use Eclipse SDK 3.6 RC4 and point my target at the downloaded location and get all plug-ins. The downloaded zip does not contain ch.qos, javax.mail.glassfish or any of the plug-ins that have errors in the image you attached. Are you sure that the Eclipse install was unzipped to a clean location and has not had any other bundles installed or placed into the Eclipse directory?
(In reply to comment #9) > I downloaded the linux RCP/RAP build from the link you provided and it contains > 426 plug-ins which all appear correctly in my target platform. I can run the > Eclipse and view the target and I can also use Eclipse SDK 3.6 RC4 and point my > target at the downloaded location and get all plug-ins. > > The downloaded zip does not contain ch.qos, javax.mail.glassfish or any of the > plug-ins that have errors in the image you attached. Are you sure that the > Eclipse install was unzipped to a clean location and has not had any other > bundles installed or placed into the Eclipse directory? I wonder if importing preferences has something to do with that. I will test again -this time I will make sure that I'm unziping eclipse in an empty-new created directory. the first installation I made, yes, I crashed an existing installation, but then I tried another directory newly created and empty.
*** Bug 321646 has been marked as a duplicate of this bug. ***
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.
