versioning - How do I set an upper bound on Gradle dynamic versions? -


i can't find explicit documentation on gradle dynamic version syntax -- examples in official docs 1.+ , 2.+, neither of appears have upper bound.

say have 1.0-snapshot , 2.0-snapshot in repository, , want project pull in first or future stable 1.x, not second.

i've tried both maven syntax ([1.0,2.0)) , ivy syntax ([1.0,2.0[). both of these pull in 2.0-snapshot. why? 2.0-snapshot considered "less than" 2.0?

on assumption, tried obvious hacks: [1.0,2.0-snapshot) , [1.0,2.0-snapshot[, both of fail dependency resolution.

how can tell gradle want version 1.x?

looks answer + includes implicit upper bound. 1.+ means "any version starts 1."

this doesn't seem anywhere in gradle docs, documented ivy:

  • end revision +
    selects latest sub-revision of dependency module. instance, if dependency module exists in revision 1.0.3, 1.0.7 , 1.1.2, "1.0.+" select 1.0.7.

Comments

Popular posts from this blog

c++ - How to add Crypto++ library to Qt project -

jQuery Mobile app not scrolling in Firefox -

How to use vim as editor in Matlab GUI -