|
Re: Why using .jar file plugins for platform fragments? [message #48608 is a reply to message #48578] |
Tue, 14 June 2005 19:50 |
Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
Some of the benefits are listed here in this document:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/plat form-core-home/documents/3.1/run_from_jars.html
An added benefit is it allow eclipse to start through java web start, which
is important for RCP.
The extracted libraries are managed by the runtime itself and do not cause
any problem.
As indicated in the document, not all plugins must or could be jared and it
is up to the plugin developer to decide on the format depending on the
restrictions.
HTH
PaScaL
"Michael Scharf" <Michael.Scharf@windriver.com> wrote in message
news:d8k16c$k9r$1@news.eclipse.org...
> Hi,
>
> when there is a shared library or an executable in a osgi .jar
> plugin, the plugin gets unpacked into the
configuration\org.eclipse.osgi\bundles
> directory.
>
> What is the advantage to install a platform fragment as .jar file
> over the classical directory distribution, where the shared library is
> accessed directly?
>
> Should plugin fragments that only contain shared libraries and executables
> be shipped as directories?
>
> Isn't this copy of libraries a potential cause of trouble?
>
> Is there a document/bugzilla entry that describes the rational
> behind this?
>
> Thanks
>
> Michael
|
|
|
|
Powered by
FUDForum. Page generated in 0.03748 seconds