Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331080 - org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.ds_1.2.0.v20100507 [2]" could not be resolved.
Summary: org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.ds_1.2.0....
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-24 23:43 EST by sarika.sant CLA
Modified: 2018-12-03 09:07 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sarika.sant CLA 2010-11-24 23:43:44 EST
Build Identifier: Version: 3.6.0, Build id: I20100608-0911

This bug seems to be resolved in IBuild I20100323 as reported in below link
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304338\

But i am getting it in 3.6  I20100608-0911.


!SESSION 2010-11-01 14:46:29.843 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=cs_CZ
Framework arguments:  -application com.teamcenter.rac.util.RegistryLoader
Command-line arguments:  -os win32 -ws win32 -arch x86 -application com.teamcenter.rac.util.RegistryLoader

!ENTRY org.eclipse.equinox.ds 4 0 2010-11-01 14:46:30.357
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.ds_1.2.0.v20100507 [2]" could not be resolved. Reason: Missing
Constraint: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
	at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)


Reproducible: Always
Comment 1 Thomas Watson CLA 2010-11-25 12:36:03 EST
Please provide steps to reproduce.  It is unclear what the issue is.  It could be a pde-build issue in building a product, a p2 problem in deploying the dependencies for ds or simply a bad configuration.  Either way this is likely not a launcher issue.  Moving to pde-build for now.
Comment 2 Lars Vogel CLA 2018-12-03 09:07:34 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.