eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking

If you use eclipse:to-maven, the resulting artifacts have poms containing versions like these, for dependencies: [3.2.0,4.0.0).

End result =>

Couldn't find a version in [3.2.0-v3232o] to match range [3.2.0,4.0.0)

I believe that to-maven needs an option like make-artifacts, to resolveVersionRanges, because stripping qualifiers means that we lose information (Eclipse 3.4 has some 3.2.0 plugins for example, but with a different qualifier than the original 3.2 Eclipse plugins).

Or the version ranges need to be fixed, something like this: [3.2.0-, 4.0.0-).

Thank you.