soften requirement limits in feature.xml <import> statements to ensure users can use DTP 1.7.x with latest Teiid 7.1.x

Looking in branches/7.1/features/org.teiid.designer.runtime.feature/feature.xml, I see that you have very restrictive limits on required imported features:

<requires>
<import feature="org.eclipse.datatools.common.doc.user" version="1.7.0.v200908280400-26-311A16321A3557"/>
<import feature="org.eclipse.datatools.connectivity.doc.user" version="1.7.0.v200908280400-37D-7733L3D753L7BBF"/>
<import feature="org.eclipse.datatools.connectivity.feature" version="1.7.0.v200908280400-7B7OAIEn1XeacwFFi4FhDyooRMY"/>
<import feature="org.eclipse.datatools.connectivity.oda.designer.feature" version="1.7.1.v200908280400-7E7C77DZRDEBDyIYEqgX"/>
<import feature="org.eclipse.datatools.connectivity.oda.feature" version="1.7.1.v200908280400-7H794CcNBC0BvEdEXZe"/>
<import feature="org.eclipse.datatools.doc.user" version="1.7.0.v200908280400-47C08w95ENAK6AFDFK7"/>
<import feature="org.eclipse.datatools.enablement.apache.derby.feature" version="1.7.0.v200908280400-7768bBmKDLfMjHuIFJW7SBI"/>
<import feature="org.eclipse.datatools.enablement.feature" version="1.7.0.v200908280400-7J8i2BWwQJOaz-Gi2C5seJM2FX2f"/>
...
</requires>

Wondering if you should explicitly include a match rule for the sake of clarity, and omit the qualifier/suffix so that you're not so brittle in your requirement.

For example, could use one of these formats:

<import plugin="org.eclipse.core.resources" version="3.2.0" match="compatible"/>

or

<import feature="org.hibernate.eclipse.feature" version="3.2.0" match="greaterOrEqual"/>