-
assigned issue to
Support for version ranges in Maven
Issue #228
resolved
Maven allows to define ranges, such as [1.0.0,]. In this case VersionEye doesn't resolve the range, but rather looks for a version named "[1.0.0,]", which is of course wrong.
This leads to false positives in the "outdated versions" tab.
Especially for libraries this is bad, as transitive dependencies might conflict with direct dependencies, unless managed manually.
Comments (3)
-
-
The server code for the resolution will be improved. Until then I can recommend to use the VersionEye Maven Plugin, it resolves the dependencies locally and only sends the results to the VersionEye API. That plugin handles the version ranges correctly.
-
- changed status to resolved
Now the pom.xml parser on the server supports version ranges as well.
- Log in to comment