|
| Re: EMF distribution size [message #424613 is a reply to message #424611] |
Fri, 31 October 2008 10:03  |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Alfred,
Comments below.
Alfred wrote:
> Hello,
> The customer I have is worried about the distibution size of EMF.
>
Are they looking at all of EMF or just the jars they're actually using.
> The customer is a rather large company with many word-wide users and the
> concern is disk space and bandwidth utilization.
>
I see.
> Is it possible to do a stripped distro and how small can it be?
>
The SDK includes things like all the source. It's a bit like comparing
a Java SDK verses just the JRE. You only need the jars of the plugins
you actually depend on so it's easy to look at those jars. Typically
people only depend on a small number of jars that add up to 2 or so Meg
for the runtime and little larger if you use EMF.Edit and EMF.Edit.UI.
Just look at your application's dependencies and add up the jar sizes.
EMF is structured as a very large number of small features, so it should
be very easy to create a distro that's minimal for your needs from the
constituent features.
Are you building an Eclipse application for your customer? If so P2 is
likely very useful and EMF's large number of small features would help
ensure that only the actually required plugins are installed.
> Alf
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02712 seconds
] 
Search
Help
Register
Login
Home
