Comment 5 for bug 779743

It partially can. Assuming you have defined a Maven property like this:

<properties>
  <spring.version>3.0.5.RELEASE</spring.version>
</properties>

then you can do something like this in the template.mf:

Import-Template:
  org.springframework.*;version="${spring.version:[=.=.=.=,+1.0.0)}"

This pretty much says: take the maven property spring.version, take it's 4 digits as lower inclusive bound and stretch the upper bound until the next major release. The result will be "[3.0.5.RELEASE,4.0.0)" in that case. So you don't need to touch the template.mf in case you update dependency versions.