Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Why doesn't a "initial@reference" bundle export packages ?
Why doesn't a "initial@reference" bundle export packages ? [message #123194] Thu, 18 December 2008 11:26 Go to next message
Jawher Moussa is currently offline Jawher MoussaFriend
Messages: 10
Registered: July 2009
Junior Member
Hi,
Would somebody please explain what does the initial@referce that is
shown for a bundle in the equinox console means ?

Example :

48 RESOLVED initial@reference:file:plugins/com.foo.module_1.0.0.jar/ [48]


The story is, I have an Eclipse RCP application which works perfectly from
Eclipse.
But once exported (using a product), I get plenty of errors on startup
because of unresolved dependencies (for bundles and packages).

I've noticed that in every case (unresolved import from a bundle A which
is exported by another bundle B), it turns out that B is marked as
"initial@reference" is the ss command output.

Doing a "b 48" on such a bundle shows that it doesn't export any package.

Cheers.
Re: Why doesn't a "initial@reference" bundle export packages ? [message #123207 is a reply to message #123194] Thu, 18 December 2008 13:36 Go to previous message
Jawher Moussa is currently offline Jawher MoussaFriend
Messages: 10
Registered: July 2009
Junior Member
Well, I think I've got it : it turned out that the "initial@reference"
bundles were exported with the wrong manifest (the one from the src file,
not the OSGi one from the project root).
Previous Topic:Declarative Services in an Eclipse Application
Next Topic:How to use OSGi bundle together with traditional plug-in?
Goto Forum:
  


Current Time: Tue Mar 19 11:04:47 GMT 2024

Powered by FUDForum. Page generated in 0.02742 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top