Encountered a problem in the project, the use of push middleware, the results using MAVEN download is not down, then directly after the manual download, copy to the local repository,
There was a problem when the results were released.
Because the release is directly on the test server, the submitted SVN code is packaged and published.
At that time had been struggling to modify the default central warehouse, add the middleware point to the warehouse, has not achieved the desired effect.
Finally suddenly brainwave, the jar package is copied directly to the SVN server's local repository to package, only to solve.
Find SVN's warehouse address first:
here. M2 is a hidden directory, so it can only be manipulated using the command line.
cd/root/.m2/repository/
Then copy the jar to the server's directory:
Then copy to the server's Maven repository.
cp/root/gexin-rp-fastjson-1.0. 0.1. jar/root/.m2/repository/com/gexin/platform/gexin-rp-fastjson/1.0. 0.1
Linux maven under the jar package download solution