force Maven to copy dependencies into target lib

Question

How do I get my project s runtime dependencies copied into the target lib folder     As it is right now  after mvn clean install the target folder contains only my project s jar  but none of the runtime dependencies

User · Answer

supposing   you don t want to alter the pom xml you don t want test scoped  e g  junit jar  or provided dependencies  e g  wlfullclient jar    here ist what worked for me    mvn install dependency copy-dependencies -DincludeScope runtime -DoutputDirectory target lib

User · Answer

If you make your project a war or ear type maven will copy the dependencies

User · Answer

If you want to deliver a bundle of your application jar  together with all its dependencies and some scripts to invoke the MainClass  look at the appassembler-maven-plugin   The following configuration will generate scripts for Window and Linux to launch the application  with a generated path referencing all the dependency jars  download all dependencies  into a lib folder below target appassembler   The assembly plugin can then be used to package the whole appassembler directory to a zip which is installed deployed along with the jar to the repository        lt plugin gt       lt groupId gt org codehaus mojo lt  groupId gt       lt artifactId gt appassembler-maven-plugin lt  artifactId gt       lt version gt 1 0 lt  version gt       lt executions gt         lt execution gt           lt id gt generate-jsw-scripts lt  id gt           lt phase gt package lt  phase gt           lt goals gt             lt goal gt generate-daemons lt  goal gt           lt  goals gt           lt configuration gt             lt  --declare the JSW config -- gt             lt daemons gt               lt daemon gt                 lt id gt myApp lt  id gt                 lt mainClass gt name seller rich MyMainClass lt  mainClass gt                 lt commandLineArguments gt                   lt commandLineArgument gt start lt  commandLineArgument gt                 lt  commandLineArguments gt                 lt platforms gt                   lt platform gt jsw lt  platform gt                 lt  platforms gt                             lt  daemon gt             lt  daemons gt             lt target gt   project build directory  appassembler lt  target gt           lt  configuration gt         lt  execution gt         lt execution gt           lt id gt assemble-standalone lt  id gt           lt phase gt integration-test lt  phase gt           lt goals gt             lt goal gt assemble lt  goal gt           lt  goals gt           lt configuration gt             lt programs gt               lt program gt                 lt mainClass gt name seller rich MyMainClass lt  mainClass gt                 lt  -- the name of the bat sh files to be generated -- gt                 lt name gt mymain lt  name gt               lt  program gt             lt  programs gt             lt platforms gt               lt platform gt windows lt  platform gt               lt platform gt unix lt  platform gt             lt  platforms gt             lt repositoryLayout gt flat lt  repositoryLayout gt             lt repositoryName gt lib lt  repositoryName gt           lt  configuration gt         lt  execution gt       lt  executions gt     lt  plugin gt     lt plugin gt       lt artifactId gt maven-assembly-plugin lt  artifactId gt       lt version gt 2 2-beta-4 lt  version gt       lt executions gt         lt execution gt           lt phase gt integration-test lt  phase gt           lt goals gt             lt goal gt single lt  goal gt           lt  goals gt           lt configuration gt             lt descriptors gt               lt descriptor gt src main assembly archive xml lt  descriptor gt             lt  descriptors gt           lt  configuration gt         lt  execution gt       lt  executions gt     lt  plugin gt     The assembly descriptor  in src main assembly  to package the direcotry as a zip would be    lt assembly gt     lt id gt archive lt  id gt     lt formats gt       lt format gt zip lt  format gt     lt  formats gt     lt fileSets gt       lt fileSet gt        lt directory gt   project build directory  appassembler lt  directory gt        lt outputDirectory gt   lt  outputDirectory gt       lt  fileSet gt     lt  fileSets gt   lt  assembly gt

User · Answer

This works for me    lt project gt           lt profiles gt       lt profile gt         lt id gt qa lt  id gt         lt build gt           lt plugins gt             lt plugin gt               lt artifactId gt maven-dependency-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt phase gt install lt  phase gt                   lt goals gt                     lt goal gt copy-dependencies lt  goal gt                   lt  goals gt                   lt configuration gt                     lt outputDirectory gt   project build directory  lib lt  outputDirectory gt                   lt  configuration gt                 lt  execution gt               lt  executions gt             lt  plugin gt           lt  plugins gt         lt  build gt       lt  profile gt     lt  profiles gt   lt  project gt

User · Answer

A simple and elegant solution for the case where one needs to copy the dependencies to a target directory without using any other phases of maven  I found this very useful when working with Vaadin    Complete pom example    lt project xmlns  http   maven apache org POM 4 0 0  xmlns xsi  http   www w3 org 2001 XMLSchema-instance      xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org maven-v4 0 0 xsd  gt        lt modelVersion gt 4 0 0 lt  modelVersion gt       lt groupId gt groupId lt  groupId gt       lt artifactId gt artifactId lt  artifactId gt       lt version gt 1 0 lt  version gt        lt dependencies gt           lt dependency gt               lt groupId gt org mybatis lt  groupId gt               lt artifactId gt mybatis-spring lt  artifactId gt               lt version gt 1 1 1 lt  version gt           lt  dependency gt       lt  dependencies gt        lt build gt           lt plugins gt               lt plugin gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                       lt executions gt                           lt execution gt                               lt phase gt process-sources lt  phase gt                                lt goals gt                                   lt goal gt copy-dependencies lt  goal gt                               lt  goals gt                                lt configuration gt                                   lt outputDirectory gt   targetdirectory  lt  outputDirectory gt                               lt  configuration gt                           lt  execution gt                       lt  executions gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt    Then run mvn process-sources  The jar file dependencies can be found in  target dependency

User · Answer

You can use the the Shade Plugin to create an uber jar in which you can bundle all your 3rd party dependencies

User · Answer

A simple and elegant solution for the case where one needs to copy the dependencies to a target directory without using any other phases of maven  I found this very useful when working with Vaadin    Complete pom example    lt project xmlns  http   maven apache org POM 4 0 0  xmlns xsi  http   www w3 org 2001 XMLSchema-instance      xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org maven-v4 0 0 xsd  gt        lt modelVersion gt 4 0 0 lt  modelVersion gt       lt groupId gt groupId lt  groupId gt       lt artifactId gt artifactId lt  artifactId gt       lt version gt 1 0 lt  version gt        lt dependencies gt           lt dependency gt               lt groupId gt org mybatis lt  groupId gt               lt artifactId gt mybatis-spring lt  artifactId gt               lt version gt 1 1 1 lt  version gt           lt  dependency gt       lt  dependencies gt        lt build gt           lt plugins gt               lt plugin gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                       lt executions gt                           lt execution gt                               lt phase gt process-sources lt  phase gt                                lt goals gt                                   lt goal gt copy-dependencies lt  goal gt                               lt  goals gt                                lt configuration gt                                   lt outputDirectory gt   targetdirectory  lt  outputDirectory gt                               lt  configuration gt                           lt  execution gt                       lt  executions gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt    Then run mvn process-sources  The jar file dependencies can be found in  target dependency

User · Answer

If you re having problems related to dependencies not appearing in the WEB-INF lib file when running on a Tomcat server in Eclipse  take a look at this   ClassNotFoundException DispatcherServlet when launching Tomcat  Maven dependencies not copied to wtpwebapps   You simply had to add the Maven Dependencies in Project Properties   Deployment Assembly

User · Answer

Just to spell out what has already been said in brief  I wanted to create an executable JAR file that included my dependencies along with my code  This worked for me    1  In the pom  under  lt build gt  lt plugins gt   I included    lt plugin gt       lt artifactId gt maven-assembly-plugin lt  artifactId gt       lt version gt 2 2-beta-5 lt  version gt       lt configuration gt           lt archive gt               lt manifest gt                   lt mainClass gt dk certifikat oces2 some package MyMainClass lt  mainClass gt               lt  manifest gt           lt  archive gt           lt descriptorRefs gt               lt descriptorRef gt jar-with-dependencies lt  descriptorRef gt           lt  descriptorRefs gt       lt  configuration gt   lt  plugin gt     2  Running mvn compile assembly assembly produced the desired my-project-0 1-SNAPSHOT-jar-with-dependencies jar in the project s target directory    3  I ran the JAR with java -jar my-project-0 1-SNAPSHOT-jar-with-dependencies jar

User · Answer

All you need is the following snippet inside pom xml s build plugins    lt plugin gt       lt artifactId gt maven-dependency-plugin lt  artifactId gt       lt executions gt           lt execution gt               lt phase gt prepare-package lt  phase gt               lt goals gt                   lt goal gt copy-dependencies lt  goal gt               lt  goals gt               lt configuration gt                   lt outputDirectory gt   project build directory  lib lt  outputDirectory gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt    The above will run in the package phase when you run   mvn clean package   And the dependencies will be copied to the outputDirectory specified in the snippet  i e  lib in this case   If you only want to do that occasionally  then no changes to pom xml are required   Simply run the following   mvn clean package dependency copy-dependencies   To override the default location  which is   project build directory  dependencies  add a System property named outputDirectory  i e       -DoutputDirectory   project build directory  lib

User · Answer

It s a heavy solution for embedding heavy dependencies  but Maven s Assembly Plugin does the trick for me      Rich Seller s answer should work  although for simpler cases you should only need this excerpt from the usage guide     lt project gt       lt build gt           lt plugins gt               lt plugin gt                   lt artifactId gt maven-assembly-plugin lt  artifactId gt                   lt version gt 2 2 2 lt  version gt                   lt configuration gt                       lt descriptorRefs gt                           lt descriptorRef gt jar-with-dependencies lt  descriptorRef gt                       lt  descriptorRefs gt                   lt  configuration gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt

User · Answer

You can use the the Shade Plugin to create an uber jar in which you can bundle all your 3rd party dependencies

User · Answer

Take a look at the Maven dependency plugin  specifically  the dependency copy-dependencies goal   Take a look at the example under the heading The dependency copy-dependencies mojo   Set the outputDirectory configuration property to   basedir  target lib  I believe  you ll have to test    Hope this helps

User · Answer

The best approach depends on what you want to do    If you want to bundle your dependencies into a WAR or EAR file  then simply set the packaging type of your project to EAR or WAR  Maven will bundle the dependencies into the right location  If you want to create a JAR file that includes your code along with all your dependencies  then use the assembly plugin with the jar-with-dependencies descriptor  Maven will generate a complete JAR file with all your classes plus the classes from any dependencies  If you want to simply pull your dependencies into the target directory interactively  then use the dependency plugin to copy your files in  If you want to pull in the dependencies for some other type of processing  then you will probably need to generate your own plugin  There are APIs to get the list of dependencies  and their location on disk  You will have to take it from there

User · Answer

The best approach depends on what you want to do    If you want to bundle your dependencies into a WAR or EAR file  then simply set the packaging type of your project to EAR or WAR  Maven will bundle the dependencies into the right location  If you want to create a JAR file that includes your code along with all your dependencies  then use the assembly plugin with the jar-with-dependencies descriptor  Maven will generate a complete JAR file with all your classes plus the classes from any dependencies  If you want to simply pull your dependencies into the target directory interactively  then use the dependency plugin to copy your files in  If you want to pull in the dependencies for some other type of processing  then you will probably need to generate your own plugin  There are APIs to get the list of dependencies  and their location on disk  You will have to take it from there

User · Answer

If you make your project a war or ear type maven will copy the dependencies

User · Answer

mvn install dependency copy-dependencies    Works for me with dependencies directory created in target folder  Like it

User · Answer

All you need is the following snippet inside pom xml s build plugins    lt plugin gt       lt artifactId gt maven-dependency-plugin lt  artifactId gt       lt executions gt           lt execution gt               lt phase gt prepare-package lt  phase gt               lt goals gt                   lt goal gt copy-dependencies lt  goal gt               lt  goals gt               lt configuration gt                   lt outputDirectory gt   project build directory  lib lt  outputDirectory gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt    The above will run in the package phase when you run   mvn clean package   And the dependencies will be copied to the outputDirectory specified in the snippet  i e  lib in this case   If you only want to do that occasionally  then no changes to pom xml are required   Simply run the following   mvn clean package dependency copy-dependencies   To override the default location  which is   project build directory  dependencies  add a System property named outputDirectory  i e       -DoutputDirectory   project build directory  lib

User · Answer

Try something like this    lt plugin gt   lt groupId gt org apache maven plugins lt  groupId gt   lt artifactId gt maven-jar-plugin lt  artifactId gt   lt version gt 2 4 lt  version gt   lt configuration gt       lt archive gt           lt manifest gt                 lt addClasspath gt true lt  addClasspath gt               lt classpathPrefix gt lib  lt  classpathPrefix gt               lt mainClass gt MainClass lt  mainClass gt           lt  manifest gt       lt  archive gt       lt  configuration gt   lt  plugin gt   lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-dependency-plugin lt  artifactId gt       lt version gt 2 4 lt  version gt       lt executions gt           lt execution gt               lt id gt copy lt  id gt               lt phase gt install lt  phase gt               lt goals gt                   lt goal gt copy-dependencies lt  goal gt               lt  goals gt               lt configuration gt                   lt outputDirectory gt                        project build directory  lib                  lt  outputDirectory gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt

User · Answer

If you re having problems related to dependencies not appearing in the WEB-INF lib file when running on a Tomcat server in Eclipse  take a look at this   ClassNotFoundException DispatcherServlet when launching Tomcat  Maven dependencies not copied to wtpwebapps   You simply had to add the Maven Dependencies in Project Properties   Deployment Assembly

User · Answer

If you want to deliver a bundle of your application jar  together with all its dependencies and some scripts to invoke the MainClass  look at the appassembler-maven-plugin   The following configuration will generate scripts for Window and Linux to launch the application  with a generated path referencing all the dependency jars  download all dependencies  into a lib folder below target appassembler   The assembly plugin can then be used to package the whole appassembler directory to a zip which is installed deployed along with the jar to the repository        lt plugin gt       lt groupId gt org codehaus mojo lt  groupId gt       lt artifactId gt appassembler-maven-plugin lt  artifactId gt       lt version gt 1 0 lt  version gt       lt executions gt         lt execution gt           lt id gt generate-jsw-scripts lt  id gt           lt phase gt package lt  phase gt           lt goals gt             lt goal gt generate-daemons lt  goal gt           lt  goals gt           lt configuration gt             lt  --declare the JSW config -- gt             lt daemons gt               lt daemon gt                 lt id gt myApp lt  id gt                 lt mainClass gt name seller rich MyMainClass lt  mainClass gt                 lt commandLineArguments gt                   lt commandLineArgument gt start lt  commandLineArgument gt                 lt  commandLineArguments gt                 lt platforms gt                   lt platform gt jsw lt  platform gt                 lt  platforms gt                             lt  daemon gt             lt  daemons gt             lt target gt   project build directory  appassembler lt  target gt           lt  configuration gt         lt  execution gt         lt execution gt           lt id gt assemble-standalone lt  id gt           lt phase gt integration-test lt  phase gt           lt goals gt             lt goal gt assemble lt  goal gt           lt  goals gt           lt configuration gt             lt programs gt               lt program gt                 lt mainClass gt name seller rich MyMainClass lt  mainClass gt                 lt  -- the name of the bat sh files to be generated -- gt                 lt name gt mymain lt  name gt               lt  program gt             lt  programs gt             lt platforms gt               lt platform gt windows lt  platform gt               lt platform gt unix lt  platform gt             lt  platforms gt             lt repositoryLayout gt flat lt  repositoryLayout gt             lt repositoryName gt lib lt  repositoryName gt           lt  configuration gt         lt  execution gt       lt  executions gt     lt  plugin gt     lt plugin gt       lt artifactId gt maven-assembly-plugin lt  artifactId gt       lt version gt 2 2-beta-4 lt  version gt       lt executions gt         lt execution gt           lt phase gt integration-test lt  phase gt           lt goals gt             lt goal gt single lt  goal gt           lt  goals gt           lt configuration gt             lt descriptors gt               lt descriptor gt src main assembly archive xml lt  descriptor gt             lt  descriptors gt           lt  configuration gt         lt  execution gt       lt  executions gt     lt  plugin gt     The assembly descriptor  in src main assembly  to package the direcotry as a zip would be    lt assembly gt     lt id gt archive lt  id gt     lt formats gt       lt format gt zip lt  format gt     lt  formats gt     lt fileSets gt       lt fileSet gt        lt directory gt   project build directory  appassembler lt  directory gt        lt outputDirectory gt   lt  outputDirectory gt       lt  fileSet gt     lt  fileSets gt   lt  assembly gt

User · Answer

The best approach depends on what you want to do    If you want to bundle your dependencies into a WAR or EAR file  then simply set the packaging type of your project to EAR or WAR  Maven will bundle the dependencies into the right location  If you want to create a JAR file that includes your code along with all your dependencies  then use the assembly plugin with the jar-with-dependencies descriptor  Maven will generate a complete JAR file with all your classes plus the classes from any dependencies  If you want to simply pull your dependencies into the target directory interactively  then use the dependency plugin to copy your files in  If you want to pull in the dependencies for some other type of processing  then you will probably need to generate your own plugin  There are APIs to get the list of dependencies  and their location on disk  You will have to take it from there

User · Answer

If you make your project a war or ear type maven will copy the dependencies

User · Answer

Take a look at the Maven dependency plugin  specifically  the dependency copy-dependencies goal   Take a look at the example under the heading The dependency copy-dependencies mojo   Set the outputDirectory configuration property to   basedir  target lib  I believe  you ll have to test    Hope this helps

User · Answer

If you want to do this on an occasional basis  and thus don t want to change your POM   try this command-line   mvn dependency copy-dependencies -DoutputDirectory   project build directory  lib  If you omit the last argument  the dependences are placed in target dependencies

User · Answer

mvn install dependency copy-dependencies    Works for me with dependencies directory created in target folder  Like it

User · Answer

It s a heavy solution for embedding heavy dependencies  but Maven s Assembly Plugin does the trick for me      Rich Seller s answer should work  although for simpler cases you should only need this excerpt from the usage guide     lt project gt       lt build gt           lt plugins gt               lt plugin gt                   lt artifactId gt maven-assembly-plugin lt  artifactId gt                   lt version gt 2 2 2 lt  version gt                   lt configuration gt                       lt descriptorRefs gt                           lt descriptorRef gt jar-with-dependencies lt  descriptorRef gt                       lt  descriptorRefs gt                   lt  configuration gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt

User · Answer

Take a look at the Maven dependency plugin  specifically  the dependency copy-dependencies goal   Take a look at the example under the heading The dependency copy-dependencies mojo   Set the outputDirectory configuration property to   basedir  target lib  I believe  you ll have to test    Hope this helps

User · Answer

Try something like this    lt plugin gt   lt groupId gt org apache maven plugins lt  groupId gt   lt artifactId gt maven-jar-plugin lt  artifactId gt   lt version gt 2 4 lt  version gt   lt configuration gt       lt archive gt           lt manifest gt                 lt addClasspath gt true lt  addClasspath gt               lt classpathPrefix gt lib  lt  classpathPrefix gt               lt mainClass gt MainClass lt  mainClass gt           lt  manifest gt       lt  archive gt       lt  configuration gt   lt  plugin gt   lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-dependency-plugin lt  artifactId gt       lt version gt 2 4 lt  version gt       lt executions gt           lt execution gt               lt id gt copy lt  id gt               lt phase gt install lt  phase gt               lt goals gt                   lt goal gt copy-dependencies lt  goal gt               lt  goals gt               lt configuration gt                   lt outputDirectory gt                        project build directory  lib                  lt  outputDirectory gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt

User · Answer

You can use the the Shade Plugin to create an uber jar in which you can bundle all your 3rd party dependencies

User · Answer

If you want to do this on an occasional basis  and thus don t want to change your POM   try this command-line   mvn dependency copy-dependencies -DoutputDirectory   project build directory  lib  If you omit the last argument  the dependences are placed in target dependencies

User · Answer

This works for me    lt project gt           lt profiles gt       lt profile gt         lt id gt qa lt  id gt         lt build gt           lt plugins gt             lt plugin gt               lt artifactId gt maven-dependency-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt phase gt install lt  phase gt                   lt goals gt                     lt goal gt copy-dependencies lt  goal gt                   lt  goals gt                   lt configuration gt                     lt outputDirectory gt   project build directory  lib lt  outputDirectory gt                   lt  configuration gt                 lt  execution gt               lt  executions gt             lt  plugin gt           lt  plugins gt         lt  build gt       lt  profile gt     lt  profiles gt   lt  project gt

User · Answer

Take a look at the Maven dependency plugin  specifically  the dependency copy-dependencies goal   Take a look at the example under the heading The dependency copy-dependencies mojo   Set the outputDirectory configuration property to   basedir  target lib  I believe  you ll have to test    Hope this helps

User · Answer

Just to spell out what has already been said in brief  I wanted to create an executable JAR file that included my dependencies along with my code  This worked for me    1  In the pom  under  lt build gt  lt plugins gt   I included    lt plugin gt       lt artifactId gt maven-assembly-plugin lt  artifactId gt       lt version gt 2 2-beta-5 lt  version gt       lt configuration gt           lt archive gt               lt manifest gt                   lt mainClass gt dk certifikat oces2 some package MyMainClass lt  mainClass gt               lt  manifest gt           lt  archive gt           lt descriptorRefs gt               lt descriptorRef gt jar-with-dependencies lt  descriptorRef gt           lt  descriptorRefs gt       lt  configuration gt   lt  plugin gt     2  Running mvn compile assembly assembly produced the desired my-project-0 1-SNAPSHOT-jar-with-dependencies jar in the project s target directory    3  I ran the JAR with java -jar my-project-0 1-SNAPSHOT-jar-with-dependencies jar

User · Answer

You can use the the Shade Plugin to create an uber jar in which you can bundle all your 3rd party dependencies

User · Answer

supposing   you don t want to alter the pom xml you don t want test scoped  e g  junit jar  or provided dependencies  e g  wlfullclient jar    here ist what worked for me    mvn install dependency copy-dependencies -DincludeScope runtime -DoutputDirectory target lib

User · Answer

The best approach depends on what you want to do    If you want to bundle your dependencies into a WAR or EAR file  then simply set the packaging type of your project to EAR or WAR  Maven will bundle the dependencies into the right location  If you want to create a JAR file that includes your code along with all your dependencies  then use the assembly plugin with the jar-with-dependencies descriptor  Maven will generate a complete JAR file with all your classes plus the classes from any dependencies  If you want to simply pull your dependencies into the target directory interactively  then use the dependency plugin to copy your files in  If you want to pull in the dependencies for some other type of processing  then you will probably need to generate your own plugin  There are APIs to get the list of dependencies  and their location on disk  You will have to take it from there

User · Answer

If you make your project a war or ear type maven will copy the dependencies

[java] force Maven to copy dependencies into target/lib

Examples related to java

Examples related to maven

Examples related to dependencies

Examples related to maven-2

Examples related to maven-3