Considered root artifact of dependency graph when looking out for cycles

Extended debug logging to mention class loader of extension in case it's different from the core loader

Used extension's original index as tiebreaker in case of equal priorities to preserve any potential semantics of input order

Introduced boolean configuration property aether.priority.implicit to use extension ordering as is

Introduced configuration properties aether.priority.* that are consulted when sorting components by their priority

Introduced DependencyCycle structure to report cyclic dependencies in CollectResult and DependencyResult

Updated maven-bundle-plugin configuration to export internal packages as well, using x-internal:=true directive

Tweaked configuration for maven-bundle-plugin to produce versioned package imports for org.apache.http.** in manifest

Bug 422413 - Simplify creation of remote repositories that employ the session's auth/proxy configuration

Added newResolutionRepositories() and newDeploymentRepository() to RepositorySystem API

Introduced config property aether.connector.persistedChecksums=true|false to control persisting of checksums

Introduced ChecksumPolicy SPI for repository connectors to consult for checksum validation

Simple refactoring transformations without logic change

Actual flow of code is somehow becoming visible. I wonder how things got this bad....

Extracted method and got rid of outer label/continue statement