Mercurial > hg > Blog
view content/Maven/assembly-vs-system-scope.md @ 90:e19bc3042ec9
draft for formatting eclipse sources using a batch tool
Proper blog post for chromecasting
author | Dirk Olmes <dirk@xanthippe.ping.de> |
---|---|
date | Tue, 23 Jan 2018 08:15:01 +0100 |
parents | 4cd9b65e10e4 |
children |
line wrap: on
line source
Title: maven-assembly-plugin vs system scope dependencies Date: 2008-04-18 Lang: en 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. 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. To package system scoped dependencies with unchanged filenames use the following snippets in your assembly descriptor: :::xml <dependencySet> <outputDirectory>lib</outputDirectory> <scope>system</scope> <outputFileNameMapping>${artifact.file.name}</outputFileNameMapping> </dependencySet>