Repository navigation
When choosing between dependency versions, use SemVer #14
Description
Activity
Do you mean "two
scijava-commonversions"? Because as things stand, nothing would ever declare a dependency onpom-scijava. (We might some day use the<scope>import</scope>with it, but right now we are not doing that.)I used the term "dependency" very sloppily. What I really meant was: when encountering different
.pomversions of the same groupId/artifactId combination, MiniMaven retains only one version:Ah OK, understood then.
MiniMaven can only handle one dependency version at a time. For example, if two
pom-scijavaversions 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.