Dear PMC,
I have a question regarding the setup of the NatTable features.
Until now we configured our features to list the dependencies to third-party libraries. For example our GlazedLists extension specifies the dependency to ca.odell.glazedlists.
This has the effect that users that install NatTable also need to install GlazedLists via Orbit themselves. Also if users create a feature based product definition, they need to ensure that the necessary third-party libraries are added with another feature (as we only specify the dependency).
Several people are complaining that a feature should contain all plug-ins that are necessary to resolve. Taking the GlazedLists example that would mean our GlazedLists extension feature should contain our NatTable extension plug-in aswell as ca.odell.glazedlists.
Such a change would make it easier to install and to consume the NatTable features. I'm just unsure if this is the way to configure a feature, since we would provide also third-party libraries directly. What is the common practice?
It would be great to get feeback on that.
For NatTable 1.4 (I'm currently working on the planning) our features would add the following:
org.eclipse.nebula.widgets.nattable.core.feature
org.eclipse.nebula.widgets.nattable.core
org.apache.commons.logging
(Eclipse related plugins should be not necessary to include)
org.eclipse.nebula.widgets.nattable.extension.glazedlists.feature
org.eclipse.nebula.widgets.nattable.extension.glazedlists
ca.odell.glazedlists
org.apache.commons.codec
org.eclipse.nebula.widgets.nattable.extension.poi
org.eclipse.nebula.widgets.richtext
org.apache.poi
org.eclipse.nebula.widgets.nattable.extension.nebula.feature
org.eclipse.nebula.widgets.nattable.extension.nebula
org.eclipse.nebula.widgets.richtext
org.eclipse.nebula.widgets.nattable.extension.e4.feature
org.eclipse.nebula.widgets.nattable.extension.e4
(Eclipse E4 CSS plugins should not be necessary to include)
Greez,
Dirk
