|Re: [jwt-dev] makeing dependencies optional|
I agree this would be great for those users who want a light-weight platform, but it may require more attention than just modifying the manifest file, I guess. I'm assuming you were talking about adding the "optional" keyword to dependencies in the manifest file. With the current code, I think JWT would simply blow up if we tried to use SVG export with, say, batik not installed. Two solutions:
Of course, we could also avoid using the OSGi "optional dependency" mechanism, and simply relocate the diagram export features in a new bundle, which would use extension points. Users could choose explicitly to install it when installing JWT in the Update manager. This would involve a bit more work, though.
Let me know if I'm missing something :)
Le mar. 08 mai 2012 18:09:57 CEST, Christian Saad a écrit :
> 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?