Mercurial > hg > Blog
annotate content/Maven/deploying-files.md @ 109:ee048ed76ea1
Datums- und Syntex Fix
| author | Dirk Olmes <dirk.olmes@codedo.de> |
|---|---|
| date | Fri, 18 Jun 2021 07:24:04 +0200 |
| parents | 1d9382b0329b |
| children |
| rev | line source |
|---|---|
| 93 | 1 Title: Deploying files with maven-deploy-plugin |
| 2 Date: 2019-02-11 | |
| 3 Lang: en | |
| 4 | |
| 5 We recently had an outage of our Nexus instance at work. The file system went corrupt, nexus would not start up properly complaining about a corrupted Orient DB. | |
| 6 | |
| 7 The blob store was largely left intact. In hindsight I should have tried to rebuild the OrientDB from the blob store using the _Repair - Reconcile component database from blob store_ task. I found out too late while I already had recovered half of our releases from my local maven repository. | |
| 8 | |
| 9 I went down the more difficult route of re-uploading artifacts from my local Maven repo into Nexus. While you can upload single artifacts through Nexus' web GUI this approach did not scale. Instead, I used the `maven-deploy-plugin` to upload. Each of our artifacts comes with source accompanied, most expose also tests and test sources. So basically an artifact consists of these files: | |
| 10 | |
| 11 * my-lib-1.0.jar | |
| 12 * my-lib-1.0.pom | |
| 13 * my-lib-1.0-sources.jar | |
| 14 * my-lib-1.0-tests.jar | |
| 15 * my-lib-1.0-test-sources.jar | |
| 16 | |
| 17 All these files need to be uploaded together at once. It took me a little while to understand how to build the commandline for the deploy plugin to accomplish this. | |
| 18 | |
| 19 The `file` parameter takes the main jar. The `pomFile` paramenter taks the pom file. That's easy. The other files have to be specified using a more convoluted format. Each file name has to specify its classifier and its type, appended to the separate `classifiers` and `types` lists. Finally the `files` list must specify the full file names. A look at the example will make more sense: | |
| 20 | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
93
diff
changeset
|
21 :::shell |
| 93 | 22 mvn deploy:deploy-file \ |
| 23 -Dmaven.repo.local=/tmp/maven-repo \ | |
| 24 -Durl=http://nexus.local/repository/releases \ | |
| 25 -DrepositoryId=releases \ | |
| 26 -Dfile=my-lib-1.0.jar \ | |
| 27 -DpomFile=my-lib-1.0.pom \ | |
| 28 -Dclassifiers=sources,tests,test-sources \ | |
| 29 -Dtypes=jar,jar,jar \ | |
| 30 -Dfiles=my-lib-1.0-sources.jar,mylib-1.0-tests.jar,my-lib-1.0-test-sources.jar | |
| 31 | |
| 32 You may have noticed that I'm specifying a separate local repository to use during the upload. This is because Maven refuses to upload artifacts from the repo it's currently operating on. Simply using a throw-away temporary local repo helps minimize the amount of fiddling around with local files. |