[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jwt-dev] makeing dependencies optional
|
Hi Marc, Yoann,
playing around a lot with Eclipse and JWT (and several other
Eclipse-based products) recently I've discovered that it might not in
all cases be desirable to force users to install very heavyweight
components such as GMF that themselves drag along many dependencies,
especially since we emphasize the customisability aspect of our
platform. Therefore, I would propose to mark the GMF dependencies (and
in the future maybe other components such as ATL/JDT?) in jwt-we (shown
below) as optional, so that the user can choose whether to install the
product and enjoy a fully featured solution or to work with a restricted
feature set but have a more light-weight platform. What do you think?
Regards,
Chris
org.apache.batik.util;bundle-version="1.6.0",
org.apache.batik.dom;bundle-version="1.6.0",
org.apache.batik.dom.svg;bundle-version="1.6.0",
org.apache.batik.svggen;bundle-version="1.6.0",
org.apache.batik.ext.awt;bundle-version="1.6.0",
org.eclipse.gmf.runtime.common.ui;bundle-version="1.5.0",
org.eclipse.gmf.runtime.draw2d.ui;bundle-version="1.5.0",
org.eclipse.gmf.runtime.draw2d.ui.render;bundle-version="1.4.1",
org.w3c.dom.svg;bundle-version="1.1.0"