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

Bug 266406

Summary:

[registry] Warning for fragment contributions to non-singleton bundle

Product:

[Eclipse Project] Equinox

Reporter:

Benjamin Muskalla <b.muskalla>

Component:

Components

Assignee:

equinox.components-inbox <equinox.components-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

enhancement

Priority:

CC:

caniszczyk, ob1.eclipse, tjwatson

Version:

3.5

Target Milestone:

3.5 M6

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
Patch	none

Description Benjamin Muskalla

2009-02-26 19:04:27 EST

N20090215-2000

Given a Bundle A and a fragment F for A.

If F tries to contribute extensions via fragment.xml while A is a non-singleton bundle this doesn't issue any warning even if the extensions are ignored.
To make it easier for developers the framework should warn about not reading the extensions in this case.

Maybe this could even be issued at development time - Chris?

Comment 1 Thomas Watson

2009-02-27 09:10:15 EST

Framework has no knowledge of extensions.  The extension registry would have to make such a warning.  Although I'm not sure we currently log an issue if a non-singleton host tries to contribute extensions.

Comment 2 Oleg Besedin

2009-03-02 15:59:33 EST

Created attachment 127225 [details]
Patch

The extension registry produces warnings (both on non-singleton fragments and bundles) but... only if the org.eclipse.equinox.registry/debug tracing option is enabled.

The patch changes code to log those warnings regardless of tracing options. (I also adjusted messages a bit.)

Comment 3 Oleg Besedin

2009-03-02 16:00:42 EST

Patch applied to CVS Head.