Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 83469 - [osgi] make osgi run from jar
Summary: [osgi] make osgi run from jar
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.1 M5   Edit
Assignee: Pascal Rapicault CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 85065
  Show dependency tree
 
Reported: 2005-01-21 17:57 EST by Pascal Rapicault CLA
Modified: 2005-02-14 09:02 EST (History)
3 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 Pascal Rapicault CLA 2005-01-21 17:57:18 EST 
It would be good to make osgi run from jars.
Comment 1 Pascal Rapicault CLA 2005-01-21 17:58:32 EST 
indeed I should have specified out of one jar.
Comment 2 Philippe Ombredanne CLA 2005-02-05 02:59:43 EST 
Are you talking about having the osgi plugins runnable when in a packaged jar
format?
That would be great!
But from my tests it looks like other plugins cannot run unpacked BTW.
Getting the whole workbench features and plugins packed as jars, with the three
OSGI plugins unpacked is not enough to get liftoff...
Comment 3 Jeff McAffer CLA 2005-02-07 23:43:02 EST 
This bug is for packaging OSGi itself as one Jar.  There is a parallel effort 
to ship all Eclipse plugins as individual jars (one per plugin).  This works 
today but is subtle.  Stay tuned for this and more fun...
Comment 4 Philippe Ombredanne CLA 2005-02-08 01:43:01 EST 
You said it works but is subtle?
Could you say anything more on it?Is it relatedd to bug 78535 ?
I also noted that jarred plugins cannot be imported using the PDE BTW.
Comment 5 Pascal Rapicault CLA 2005-02-08 08:51:42 EST 
Startup.jar (in cvs: org.eclipse.platform) will fail unless you specify various
properties (osgi.framework, the classpath of the fwk).

If you want to use osgi standalone (without startup.jar) you should be fine. In
fact you may even consider using the DefaultAdaptor
Comment 6 Pascal Rapicault CLA 2005-02-11 17:20:14 EST 
I released a set of changes to OSGi and to startup.jar to enable that. However
due to the bug #85013, we can't ship eclipse as a jar yet.
Comment 7 Philippe Ombredanne CLA 2005-02-11 18:58:42 EST 
Yeeha! :-)
But you could still ship it jars, if you do not pacakge the PDE with it.
Correct?
Which milestones does it go into? M5?
Comment 8 Jeff McAffer CLA 2005-02-11 20:37:38 EST 
Eclipse cannot ship as jars until the whole story holds together.  Users are 
free of course to take plugins and jar them up and ship them but there are, as 
yet, not guarantees that this works.  The test suites have not been run, we 
don't use it that way etc etc.  Summary:  Your enthusiasm for this is great but 
we are not done yet.

Pascal, can this report be closed?  Bug 85013 is a general problem not specific 
to osgi no?
Comment 9 Pascal Rapicault CLA 2005-02-14 09:02:08 EST 
Closing since it is now possible. 
Until osgi ships as jar, people willing to do that must:
- extract all the jars from org.eclipse.osgi into one folder
- jar the resulting folder such that the classes are at the root of the jar:
     org.eclipse.osgi.jar
       org/
         eclipse/
          ....
       META-INF/
         MANIFEST.MF