Support for GMF should be packaged into a separate feature

[eclipse-diffmerge-bot]

I tried to setup a simple target with just Eclipse, EMF and Diff/Merge, but it seems I am forced to install GMF too. Please exclude the GMF support from the main feature and offer it separately.

🆔 ECLIPSE-439170 👷 felix.dorner 📅 2014-07-08 🔎 0.3.0

[eclipse-diffmerge-bot]

olivier.constant commented on 2014-08-19

There is currently one feature, which is tailored for an Eclipse Modeling environment. The thing is, one could also ask for a feature with only the diff/merge engine and no GUI, then the GUI, then GMF... And we end up at the granularity of plugins.
Cannot you just create your own feature so that it exactly fits your need?

olivier.constant commented on 2014-08-27

Felix,
Any reaction on your side or should I close the entry?

felix.dorner commented on 2014-08-27

Another argument is that maybe potential users that would like to try out diff/merge might be turned away, thinking that GMF seems to be a hard requirement even if it's not. I don't strictly need this, so if you're not convinced, feel free to close.

stephane.bouchet commented on 2014-10-02

Hi,
i agree with Felix about more granularity.
In my case, i created my own feature with the strict minimum plugins.

I do not think having a feature that contains only one plugin is a big deal.
And yes, it will create 3 features Runtime, UI and GMF.

olivier.constant commented on 2015-05-29

The post-Mars release will have a revised packaging due to SCM support. I think that will be a good opportunity to redefine the granularity of features.

olivier.constant commented on 2017-04-20

This is currently fixed in master as a result of the refactoring of features.

olivier.constant commented on 2017-12-19

Integrated in v0.9.0, closing.

olivier.constant commented on 2017-12-19

(In reply to olivier.constant from comment #7)

Integrated in v0.9.0, closing.

Actually, in v0.8.0.