Different repositories used by Maven and Gradle samples

[wilkinsona]

The Maven samples use http://repo.spring.io/release, http://repo.spring.io/milestone and http://repo.spring.io/snapshot for plugins, and http://repo.spring.io/milestone and http://repo.spring.io/snapshot for dependencies.

The Gradle samples use mavenLocal and http://repo.spring.io/libs-snapshot for plugins, and varying combinations of mavenLocal, mavenCentral and http://repo.spring.io/libs-snapshot dependencies.

[wilkinsona]

Is it worth limiting the list of repositories to what's needed? Just use http://repo.spring.io/release for Boot releases, add http://repo.spring.io/milestone for Boot milestones and add http://repo.spring.io/snapshot for Boot snapshots? It's more work as part of the release process, but it does the "right thing" of keeping the number of repositories down.

Another option would be to use http://repo.spring.io/libs-release for releases, http://repo.spring.io/libs-milestone for milestones and http://repo.spring.io/libs-snapshot for snapshots and take advantage of Artifactory's virtual repositories. It's a single repository, no matter if it's a release, a milestone, or a snapshot, but it still requires changes as part of the release process.

Yet another option is that it's just not worth worrying about. @philwebb, this probably affects you the most as it potentially complicates the release process.

[dsyer]

My opinion: master needs to have the repo.spring.io declared for plugins and normal dependencies. The release should have everything in Central. It makes the relase process more complicated, but it's the only sane end state. BTW I think this is a duplicate of #419?

[philwebb]

For now I have simply declared all of them, with a note indicating that users should really limit their own selection. The main reason for taking this approach is that I won't have time to put together a solution that updates the files during the release process before we go GA.

It might be a good solution anyway, since users might grab the sample build from GitHub master, even though they are using a release version.

Feel free to raise another issue if we want a better approach for 1.1