Eclipse Community Forums: Rich Client Platform (RCP)

Home » Eclipse Projects » Rich Client Platform (RCP) » Why is bundeling prefered

Why is bundeling prefered [message #1350608]

Mon, 12 May 2014 14:54

Eclipse User

Hey all,

i read a lot of times that if you have an external jar, it is recommended to bundle it instead of adding it to the classpath in the Runtime tab of the manifest, but i could not find some reasons for this. In fact when i´m bundeling an external jar files, the bundle does the same (adding it to classpath in the runtime tab and export any package) so where is the difference?

Thanks for any reason or advice Wink

Greetz
Thomas

Re: Why is bundeling prefered [message #1350796 is a reply to message #1350608]

Mon, 12 May 2014 16:41

Eclipse User

Rebundleing is better IMHO if multiple bundles in your env need it,
adding to your MANIFEST only makes sense it really is only used
internally - if it is part of ANY public API rebundleing is the way to go!

Tom

On 12.05.14 20:54, T. Wilhelm wrote:
> Hey all,
>
> i read a lot of times that if you have an external jar, it is
> recommended to bundle it instead of adding it to the classpath in the
> Runtime tab of the manifest, but i could not find some reasons for this.
> In fact when i´m bundeling an external jar files, the bundle does the
> same (adding it to classpath in the runtime tab and export any package)
> so where is the difference?
> Thanks for any reason or advice ;)
> Greetz Thomas

Re: Why is bundeling prefered [message #1351733 is a reply to message #1350796]

Tue, 13 May 2014 02:19

Eclipse User

If you want to use standard jar, you can also check this Eclipse project : Orbit
The goal is to provide directly a repository of bundled versions of third party libraries.

Previous Topic:	Eclipse failed to run Installed Plug-ins
Next Topic:	How to add build ID in about dialog.

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 13 19:35:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter