Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319323

Summary:	Framework Extension bundles that end with "_.jar" are not resolved
Product:	[Eclipse Project] Equinox	Reporter:	Andy McCright <andymc>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	tjwatson
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Andy McCright

2010-07-08 17:32:46 EDT

Build Identifier: Equinox 3.6 RC2

After upgrading from Equinox 3.2.1 to 3.6, class sharing stopped working for bundle classes - for more info on class sharing, we are using the com.ibm.cds_*.jar from http://www.ibm.com/developerworks/java/library/j-ibmjava4/ .

We truncated the com.ibm.cds_*.jar file name to just "com.ibm.cds_.jar" in order to remove the version information from the jar file name (this file was also truncated when we ran successfully on Equinox 3.2.1).

Without changing the config.ini file, we received the following message in our .log file:
!ENTRY org.eclipse.osgi 4 0 2010-07-01 14:51:44.760
!MESSAGE Bundle com.ibm.cds not found.

We could avoid this by changing this line in config.ini:
from osgi.framework.extensions=com.ibm.cds
to osgi.framework.extensions=reference:file:com.ibm.cds_.jar

Class sharing worked at this point, but after starting with a -clean option, the framework would fail to start - message in the .log file looked like:
!ENTRY org.eclipse.core.launcher 4 0 2010-07-07 16:02:57.857
!MESSAGE Could not find extension: reference:file:com.ibm.cds_.jar

Tom suggested renaming the file to com.ibm.cds.jar and using the original config.ini entry.  This seems to work.

Renaming the file is no problem, but I thought I would open a bug in case others hit this problem.

Reproducible: Always

Steps to Reproduce:
1. Install eclipse 3.6 RC2
2. Drop the com.ibm.cds_.jar file into the plugins directory.
3. Add this following line to config.ini:
osgi.framework.extensions=com.ibm.cds

Comment 1 Thomas Watson

2010-07-09 10:34:07 EDT

I think this may also have something to do with p2, although I am pretty sure the launcher has a bug when search for the extension as well.  Since you are just placing the extension in the plugins/ folder and updating the config.ini manually to add the osgi.framework.extenions property p2 has no knowledge of this extension and I think it may be getting confused.

Comment 2 Eclipse Webmaster

2019-09-06 16:17:33 EDT

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.

Comment 3 Eclipse Genie

2021-09-05 14:23:01 EDT

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.