![simple coords 1.7.10 simple coords 1.7.10](https://minecraftdls.com/wp-content/uploads/2015-02-05_11.21.16.png)
On the edge, latest release, no downgrade.ġ.5, or failure if another strict or higher require constraint disagrees.ġ.5 or a patch version of it exclusively. Overwrites versions from transitive dependencies.Īny version between 1.0 and 2.0 (exclusive) except for 1.4, 1.5 if nobody else cares. Tested with 1.5, but follows semantic versioning.Īny version between 1.0 and 2.0 (exclusive), 1.5 if nobody else cares.
![simple coords 1.7.10 simple coords 1.7.10](http://img.file-minecraft.com/img/Xaeros-Minimap-Mod-2.jpg)
Tested with 1.5, soft constraint upgrades according to semantic versioning.Īny version between 1.0 and 2.0, 1.5 if nobody else cares. Tested with version 1.5, believe all future versions should work.Īny version starting from 1.5, equivalent of org:foo:1.5. Rich version use cases Which version(s) of this dependency are acceptable?
#SIMPLE COORDS 1.7.10 HOW TO#
The following table illustrates a number of use cases and how to combine the different terms for rich version declaration: Table 7. The build enforces the version of the dependency. The dependency has a dynamic version, and some versions did not match the requested attributes. There is a rich version with a strictly in the graph which enforces the version of this dependency.Ī dependency resolution rule overruled the default selection process.Ī ComponentSelection.reject rejected the given version of the dependency
![simple coords 1.7.10 simple coords 1.7.10](https://i.ytimg.com/vi/GePZXzox-mw/hqdefault.jpg)
This resulted in conflict resolution to select the most appropriate version.Ī dependency constraint participated in the version selection. The dependency appeared multiple times in the graph, with different version requests. The dependency appears in the graph, with a rich version containing one or more reject.īy conflict resolution : between versions This can also be followed by a because text. The dependency appears in the graph, with a dynamic version, which did not include the listed versions. The dependency appears in the graph, and the inclusion came with a because text. This means that no other reason than having a reference, direct or transitive, was present Have a look at the table below to understand the meaning of the different terms used: Table 5. The "Selection reasons" part of the dependency insight report will list the different reasons as to why a dependency was selected. To some extent, this is similar to an abstract class ( canBeResolved=false) which is not supposed to be instantiated, and a concrete class extending the abstract class ( canBeResolved=true).Ī resolvable configuration will extend at least one non-resolvable configuration (and may extend more than one). It is an error to try to resolve a configuration which has canBeResolved set to false. The reason is that depending on the usage (compile classpath, runtime classpath), it can resolve to different graphs. Such a configuration is there only to declare dependencies. That is to say we’re going to compute a dependency graph, resolve the components in the graph, and eventually get artifacts.Ī configuration which has canBeResolved set to false is not meant to be resolved. This distinction is represented by the canBeResolved flag in the Configuration type.Ī configuration that can be resolved is a configuration for which we can compute a dependency graph, because it contains all the necessary information for resolution to happen.