Hey guys, i believe there is a bug in either the way versions for
dependencies are matched or in the way the eclipse:to-maven plugin
works.
When I run the eclipse:to-maven target, my brand new repository is
populated with eclipse plugins and nothing else. I attempt to build a
project which depends on these dependencies, but the dependencies do not
resolve. One of the eclipse plugins depends on another one that is
within version range [3.3.0,4.00). The dependecny i have to satisfy
this version is 3.3.0-3.3.0-I20070605-0010. But this is not acceptable,
yielding this error:
org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a
version in [3.3.0-I20070605-0010, 3.2.0-I20060605-1400] to match range
[3.3.0,4.0.0)
I understand that maven might desire some sort of special versioning in
the form of x.y.z, in which case the eclipse:to-maven plugin should
setup the pom's correctly (set the versions in an acceptable manner.)
If maven does not have this hard and fast version requirement, shouldn't
it accept the version 3.3.0-I20070605-0010, 3.2.0-I20060605-1400 to be
within 3.3.0-4.0.0?
Thank you
Apaar Trivedi
Consultant
Blue Fish Development Group
http://www.bluefishgroup.com <http://www.bluefishgroup.com/>
Blue Fish is Hiring! Check out www.bluefishgroup.com/careers
<http://www.bluefishgroup.com/careers>
