MavenResource can not resolve artifacts without explicit repository configuration

[dsyer]

MavenResource has a static parse() method that takes a String as an argument. But it uses a default instance of MavenProperties that has no repositories configured, so it is doomed to fail. It even fails when the resource has already been downloaded and is cached locally. I'd prefer it if the default behaviour was more like you get from Maven (or even better, more like that you get in the Spring Boot CLI - it adds the Spring repos, and the local cache as well as Central by default, and also parses the user's settings.xml).

[markpollack]

We had explicitly decided not to include any location, in part thinking of the PCF deployment case where folks typically point to their own in-house repo and to not bring an opinion to the table. Granted maven central isn't a big opinion, and we could potentially override the default at the SCDF level. Thoughts @markfisher