Hi, hdockter wrote: >> 5. resolve project dependencies on 3rd party libs (against mavenrepoo) > >> 6. freeze (remember) versions of 3rd party libs on project release >> (repeatable build) > > I don't understand 5 and 6.
5 is about downloading dependencies from (maven) repositories to project (lib) directory, as gradle is built on top of ivy I guess it does so. 6 is about the following scenario (though it's not exactly the case for enterprise projects) I can describe module dependency on *latest* (snapshot) version of the particular library. But once I made a release, I want snapshot dependency to be resolved (and frozen) to the *exact* version of the particular library. So I need build task which resolves all "snapshot" dependencies to exact ones. This can be done in form of two dependency sets one with "soft" versions (snapshots) allowed and another with "hard" versions (all "soft" versions resolved to concrete ones). "hard" versions set should be updated by "release" task only. (more elegant solution is appreciated) -- View this message in context: http://www.nabble.com/using-maven-repos-with-gradle-tp19391276p19434485.html Sent from the gradle-user mailing list archive at Nabble.com.
