…in the bundle This assumes http, which is bad, but, this makes getting up and running easier
Not a big fan of the name RepositoryURLFinder, it is closer to a Facade or a Util class, but those names do not fit.
A Repository can already figure out most information about itself, it should know what the content URL is. However this is a double edge sword, and I'm not sure this is the best place for it. Another option would be to stick this logic in a Util class, The problem with that, is that the Util class would need to be a component, as we need access to the GlobalRestConfig, and the RepositoryTypeRegistry to figure out the content URL. Other thoughts ?
…reate an initialized repository object. Also, updated Template, TemplateSet, and TemplateProvider to expose generic type.
…y that 1st one
…fixed by Peter)
… whole previous snapshot stuff (it references 1.9.2-SNAPSHOT for god sake!)
…y problems with Restlet Client.
… in that case current version is better than old snapshot. Or, it should point to a release version. All in all, what there was before this change was bad for sure.
…s() - instead just check for non null status. Remember if a service url does not include a trailing slash then Nexus may respond with 301 redirect
…eft open. Also, a copy+paste of this same code to be found in one IT.
…elease in finally, etc)
…t and replace it with Guava libraries.
… pass once issue fixed. Note: launcher's RequestFacade class was modified to make possible performing conditional GETs. Despite lot of changes (Reformat), it is only one method separated in two, and exposing sendMessage( final Request request, final org.hamcrest.Matcher<Response> matchers ), while the method with "old" signature only constructs the Request.
…xed AbstractNexusTask to work well with tasks handling TaskInterruptedEx (not letting them propagate).