Depends on #43. Please merge the 0.0.2-SNAPSHOT PR #43 first. I've already performed the deployment for 0.0.1 that this enables through another branch, then have merged it over to this PR for master. We only need this code when we do a subsequent deployment.
Travis uses a NAT which means each outgoing request may come from different IP address.
Sonatype uses fingerprinting including IP address to determine a correlate a connecting client's requests, in order to place resources from the same client within the same dynamically-created staging repository.
These two together mean that deployment results in split staging repositories, with one per IP address that was used.
This pull request changes to use nexus-staging-maven-plugin instead of maven-deploy-plugin. This plugin, from Sonatype, performs additional work to explicitly create a staging repository and then explicitly deploy to that repository.
Depends on #43. Please merge the 0.0.2-SNAPSHOT PR #43 first. I've already performed the deployment for 0.0.1 that this enables through another branch, then have merged it over to this PR for master. We only need this code when we do a subsequent deployment.
These two together mean that deployment results in split staging repositories, with one per IP address that was used.
This pull request changes to use
nexus-staging-maven-plugininstead ofmaven-deploy-plugin. This plugin, from Sonatype, performs additional work to explicitly create a staging repository and then explicitly deploy to that repository.