| Third-party JARs in a separate plugin [message #322621] |
Wed, 21 November 2007 13:48  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
I've seen several times the recommendation to put JARs that my plugin(s)
depends on in a separate plugin. Is there any documentation on the
reasoning behind this recommendation? My client is considering to ignore
the recommendation and I'm trying to assemble a list of potential
problems with bundling the JARs in the main plugin so we can make a
properly informed decision.
Thanks,
Eric
|
|
|
|
| Re: Third-party JARs in a separate plugin [message #322728 is a reply to message #322624] |
Tue, 27 November 2007 10:05  |
| Eclipse User |
|
|
|
Originally posted by: Jim.Cooper.sas.com
A couple of the biggest reasons are conflicts and duplication.
If you have 14 plugins that all need foobar.jar, you can put foobar.jar
in a separate plugin, and only have 1 copy of it around, as opposed to
having 14 copies of it, which you have to keep all in sync.
The conflicts come in where the plugins get loaded, and the one with
foobar.jar v1.1 gets loaded first, then another plugin gets loaded later
and needs foobar.jar v1.5... if foobar.jar v1.1 is found on the
classpath first, v1.5 won't be seen, and you can wind up with
ClassNotFound errors, etc.
Paul Webster wrote:
> In some cases the 3rd party jar license requires the ability for users
> to be able to swap it out, which is doable if 3rd party jars are all
> turned into separate 3rd party plugins.
>
> There's also the growth aspect to consider. If the product ever goes
> from one massive plugin to several plugins (some UI, some core, some
> library) then it might also be reasonable to assume that some of the 3rd
> party libraries might need to be updated (and/or patched) separately.
>
> I'm sure there are many other reasons.
>
> PW
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04705 seconds
Home