When choosing between dependency versions, use SemVer

[dscho]

MiniMaven can only handle one dependency version at a time. For example, if two pom-scijava versions are specified in the dependency tree, only one is used.

We should assume that SemVer is in effect, and use the newer of both dependency versions if the major version agrees.

When the major version disagrees, we should go with the newer one but complain really loudly.

[ctrueden]

Do you mean "two scijava-common versions"? Because as things stand, nothing would ever declare a dependency on pom-scijava. (We might some day use the <scope>import</scope> with it, but right now we are not doing that.)

[dscho]

I used the term "dependency" very sloppily. What I really meant was: when encountering different .pom versions of the same groupId/artifactId combination, MiniMaven retains only one version:

minimaven/src/main/java/org/scijava/minimaven/MavenProject.java

Line 1053 in ea1092b

String key = dependency.getKey();

[ctrueden]

Ah OK, understood then.