| Summary: | stem.product for Eclipse 3.3 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] STEM | Reporter: | John Thomas <jthomas119> | ||||||||
| Component: | Internal | Assignee: | John Thomas <jthomas119> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | Daniel Ford <webdaford> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | webdaford | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows XP | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
John Thomas
committed The latest checked in version of stem.product has the following plugins listed that are not installed in my version of eclipse 3.3. If they are truly required then the install document needs to be updated to require the additional install of the related products. <plugin id="org.eclipse.jem.util"/> <plugin id="org.eclipse.jst.jsp.core"/> <plugin id="org.eclipse.jst.pagedesigner.jsp.core"/> <plugin id="org.eclipse.wst.common.core"/> <plugin id="org.eclipse.wst.common.emf"/> <plugin id="org.eclipse.wst.common.emfworkbench.integration"/> <plugin id="org.eclipse.wst.common.environment"/> <plugin id="org.eclipse.wst.common.frameworks"/> <plugin id="org.eclipse.wst.common.project.facet.core"/> <plugin id="org.eclipse.wst.common.uriresolver"/> <plugin id="org.eclipse.wst.css.core"/> <plugin id="org.eclipse.wst.html.core"/> <plugin id="org.eclipse.wst.sse.core"/> <plugin id="org.eclipse.wst.validation"/> <plugin id="org.eclipse.wst.xml.core"/> Also it included org.eclipse.jdt.compiler.apt org.eclipse.jdt.internal.compiler.tool which cause warning messages because they require Java 6. *** Bug 182037 has been marked as a duplicate of this bug. *** regenerated the configuration to 67 core plugins comitted This version may be shorter but it does not support Help Contents, BIRT or GoogleEarth. I am reopening the bug. I am prepariing a new version and a Readme file documenting why various plugins are included. John Created attachment 65776 [details]
New stem.product with support for BIRT/Help/GE
Don't close this after committing it. I want to finish the documentation of it.
Committed The bundle exception I was getting before is now back. org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: org.eclipse.equinox.common_3.3.0.v20070318 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:631) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:505) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:279) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:465) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:189) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:291) (In reply to comment #10) > Committed > The bundle exception I was getting before is now back. > > > org.osgi.framework.BundleException: The bundle could not be resolved. Reason: > Another singleton version selected: org.eclipse.equinox.common_3.3.0.v20070318 > at > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305) > at I didn't get that exception. Where do you get it. When you invoke STEM or when you do something specific? Strange, I reverted back to the stem.product that is in CVS (because I had already modified my version and now I get an exception (but different) It was working before java.lang.NoClassDefFoundError: org/eclipse/core/runtime/ISafeRunnable at org.eclipse.jface.databinding.swt.SWTObservables.getRealm(SWTObservables.java:73) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:458) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ohf.stem.core.common.presentation.CoreEditorAdvisor$Application.start(CoreEditorAdvisor.java:111) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146) Even stranger: I went to my sister stem workspace that mirrors the CVS image (I use it as a backup and place to test patches) I updated it to the latest HEAD status including stem.product (1.9) It works fine. I think that there is some side effect of the product file that I don't understand. By the way, the schedule for 3.3M7 is May 4th so we may have a new set of problems (or solutions) tomorrow. I hope they fix the debugger... I was unable to figure out how to fix the problem. I finally blew away my .metadata file and rebuilt the workspace. Now it seems to work OK. I think that this was an eclipse problem and something in the metadata got messed up. Do you mean you created a different workspace and then started fresh from the CVS repository? Or something different? No, I could have rebuilt a new workspace from CVS but I had a couple of in process things I did not want to lose so I did the following: - stop eclipse - rename .metadata (in case I wanted to waste another day on the problem) - start eclipse - import from existing project - For each project use team to sync with cvs (I forget the menu item for this) Were you able to get past the problem that you had with "Singleton ... org.eclipse.equinox.common" I think that it is related to my problem with ISafeRunable because ISaveRunalble is in org.eclipse.equinox.common.jar John No, the BundleException is back. I'm ignoring it right now. I tend to think it isn't a "real" problem, just something is misconfigured. It went away once already when I blew away stem.product and recreated it, but then I lost the help plugins (which I needed). Created attachment 67519 [details]
add org.eclipse.core.net to stem.product
It appears that org.eclipse.core.net is required in order to export the RCP.
This patch adds it to stem.product.
Dan, since you are building with 3.3M6 I don't think that it is required but maybe won't hurt to have it. It was required for the Linux build also but I have not yet created a patch file for the stemLinux.product file.
committed addition of org.eclipse.core.net Created attachment 67845 [details] delete the stem.product.readme - moved to wiki info now in wiki http://wiki.eclipse.org/index.php/Installation_Guide#Understanding_stem.product This can be closed closed Comment on attachment 65776 [details]
New stem.product with support for BIRT/Help/GE
flagged for iplog
Comment on attachment 67519 [details]
add org.eclipse.core.net to stem.product
flagged for iplog
Comment on attachment 67845 [details]
delete the stem.product.readme - moved to wiki
flagged for iplog
|