Mercurial > hg > Blog
comparison content/Maven/assembly-vs-system-scope.md @ 0:4cd9b65e10e4
initial import of the pelican based blog
| author | Dirk Olmes <dirk@xanthippe.ping.de> |
|---|---|
| date | Fri, 28 Jun 2013 08:48:58 +0200 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:4cd9b65e10e4 |
|---|---|
| 1 Title: maven-assembly-plugin vs system scope dependencies | |
| 2 Date: 2008-04-18 | |
| 3 Lang: en | |
| 4 | |
| 5 I was playing around with [Gigaspaces](http://www.gigaspaces.com/) the other day. Since GS jars are not available on any Maven repo and GS comes with everything you need prepackaged I used Maven dependencies with system scope to pull the required jars into my build. | |
| 6 | |
| 7 Then I tried to assemble a simple zip to move some code over to another machine and created an assembly descriptor to build a deployment package. One requirement was to keep the Gigaspaces jars in their original form i.e. no renaming, unpacking etc. | |
| 8 | |
| 9 To package system scoped dependencies with unchanged filenames use the following snippets in your assembly descriptor: | |
| 10 | |
| 11 :::xml | |
| 12 <dependencySet> | |
| 13 <outputDirectory>lib</outputDirectory> | |
| 14 <scope>system</scope> | |
| 15 <outputFileNameMapping>${artifact.file.name}</outputFileNameMapping> | |
| 16 </dependencySet> |