Plugin upload appears to be successful when misconfigured

[michaelmelody91]

When specifying configuration to upload a definition to an on-prem SwaggerHub instance with an incorrect base path, the upload is logged as successful. When verifying in SwaggerHub, the API is unavailable and cannot be found.

Sample output for this issue:

[DEBUG] Configuring mojo 'io.swagger:swaggerhub-maven-plugin:1.0.6:upload' with basic configurator -->
[DEBUG]   (f) api = test-upload
[DEBUG]   (f) basepath = /bad-basepath
[DEBUG]   (f) branch = SWAGGERHUB
[DEBUG]   (f) enableScmIntegration = true
[DEBUG]   (f) format = json
[DEBUG]   (f) host = 11.10.1.96
[DEBUG]   (f) inputFile = target/swagger/swagger.json
[DEBUG]   (f) isPrivate = true
[DEBUG]   (f) owner = CC_Freestyle_Org
[DEBUG]   (f) port = 80
[DEBUG]   (f) protocol = http
[DEBUG]   (f) skipFailures = false
[DEBUG]   (f) token = e**********************************7
[DEBUG]   (f) uploadType = inputFile
[DEBUG]   (f) version = 2.5.14.0
[DEBUG] -- end configuration --
[INFO] Uploading to 11.10.1.96, basepath: /bad-basepath: api: test-upload, owner: swagger-owner, version: 2.5.14.0, inputFile: target/swagger/swagger.json, format: json, isPrivate: true, definitionDirectory: null, definitionFileNameRegex: null, uploadType: inputFile, skipFailures: false, token: e**********************************7
[DEBUG] Executing input file based upload...
[INFO] Uploading API name test-upload version 2.5.14.0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS