Skip to content
This repository was archived by the owner on Oct 31, 2022. It is now read-only.

Conversation

jkasten2
Copy link
Member

@jkasten2 jkasten2 commented Apr 8, 2018

  • When both an exact version and range are defined pin to exact version if in range instead of changing range bounds
  • Example version '1.5.0' and '[1.0.0, 1.99.99]' will result in '1.5.0'
  • This does not work in all nested cases yet with gms and android.support for example
    • "GMS pining when in version range - GMS in sub project - Gradle 4_6" test cases is an example of this issue case
  • For reference this is to change some of the logic introduced in PR Version ranges are kept instead of using highest #29
  • Changed def to String where they could not be inferred to fix Intellij type checks

History
Extra debugging dd33241

* When both an exact version and range are defined pin to exact version if in range instead of changing range bounds
* Example version '1.5.0' and '[1.0.0, 1.99.99]' will result in '1.5.0'
* This does not work in all nested cases yet with gms and android.support for example
   - "GMS pining when in version range - GMS in sub project - Gradle 4_6" test cases is an example of this issue case
@jkasten2 jkasten2 changed the title Exact versions pin in range instead of limiting it Pin exact version when in range instead of changing bounds Apr 8, 2018
* Changed / fixed logic on calculating what version to align to;
* Fixed issue where child projects were omitted
   - Example: main app sets gms:[11.2.0, 11.8.0] & the sub project sets 11.4.0 then 11.4.0 will be use
   - This was fixed with configuration.copyRecursive()
* Now omits version pining for modules under Google's modules. GMS, Firebase, and support.
   - Uses configuration.incoming.resolutionResult to check the parent to skip
   - Example gms:play-services-basement:11.2.2 depends on com.android.support:25.2.0
* Added com.android.tools.build:gradle:3.1.0 to build.gradle so IntelliJ can inspect android types
@jkasten2 jkasten2 force-pushed the version_range_pining branch from dd33241 to bb732c5 Compare April 9, 2018 11:56
@jkasten2 jkasten2 force-pushed the version_range_pining branch from 6fe8f8c to 3c03669 Compare April 10, 2018 09:07
@jkasten2 jkasten2 merged commit 60fbbb2 into master Apr 11, 2018
@jkasten2 jkasten2 deleted the version_range_pining branch April 11, 2018 05:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant