Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346957 - org.eclipse.equinox.registry in 3.7RC2 does not contain runtime_registry_compatibility.jar
Summary: org.eclipse.equinox.registry in 3.7RC2 does not contain runtime_registry_comp...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tobias Oberlies CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 06:09 EDT by Hugues Malphettes CLA
Modified: 2021-04-28 16:54 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hugues Malphettes CLA 2011-05-24 06:09:13 EDT 
When we build eclispe RTP against the 3.7RC2 version of the eclipse p2 repo I noticed the warning:
[WARNING] Could not read bundle entry /home/hmalphettes/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.registry/3.5.100.v20110502/org.eclipse.equinox.registry-3.5.100.v20110502.jar!/runtime_registry_compatibility.jar


http://download.eclipse.org/eclipse/updates/3.7milestones/S-3.7RC2-201105191138/plugins/org.eclipse.equinox.registry_3.5.100.v20110502.jar

And indeed it does not contain a runtime_registry_compatibility.jar
although it does mention it in the manifest:
Bundle-ClassPath: runtime_registry_compatibility.jar, .

I have not faced any problem at runtime so far that would be related to this.
Comment 1 Thomas Watson CLA 2011-05-24 08:58:59 EDT 
This jar is provided by the org.eclipse.core.runtime.compatibility.registry fragment bundle.  Not having the jar just means you are missing some old deprecated APIs from core.runtime.  I am guessing this warning comes from PDE.  Moving it there for confirmation.  But I don't think there is anything to fix here since it is just a warning, and one that we likely do not want to remove because it could indicate a real issue for other cases.
Comment 2 Andrew Niefer CLA 2011-05-24 11:06:52 EDT 
I think this is UI's warning
Comment 3 Hugues Malphettes CLA 2011-05-24 21:02:17 EDT 
The warning comes from tycho (the set of maven plugins to build with p2).
You can see it here:
Open https://hudson.eclipse.org/hudson/job/rtp-packages/148/consoleFull
The search for "[WARNING]"

It sounds like this is expected, so I would move this bug to tycho or mark it as WONTFIX.

Thanks for your attention.
Comment 4 Igor Fedorenko CLA 2011-05-25 08:31:42 EDT 
This messages warns about missing Bundle-ClassPath entries. Such entries
could either be a placeholder for a "patch" fragment (see [1]) or it
could be an indication of a problem with the bundle. Tycho can't tell
the two apart and issues the warning. I do agree the message can be confusing, so feel free to reopen the bug if you can suggest a better approach.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=126687#c9
Comment 5 Tobias Oberlies CLA 2011-06-03 05:32:21 EDT 
Since missing entries on the Bundle-ClassPath are explicitly allowed by the OSGi spec (see discussion on TYCHO-577 [1]), Tycho shouldn't issue a warning in this case.

Therefore I've changed the severity of that message to debug in commit e39cf27.

[1] https://issues.sonatype.org/browse/TYCHO-577?focusedCommentId=128918&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_128918