The difference is that the Maven Assembly Plugin will automatically copy all required dependencies into a jar file.
#How to install maven jar in eclipse manual
Similarly to the manual approach, we need to provide the information about the main class. Let's take a look at the configuration in pom.xml:
The main goal in the assembly plugin is the single goal, which is used to create all assemblies (all other goals are deprecated and will be removed in a future release). The Apache Maven Assembly Plugin allows users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single, runnable package. The advantages and disadvantages of this approach are: Please note that we need to provide a fully qualified name of the class, which means it will include package name. We add a classpath, with all dependencies (folder libs/), and provide the information about the main class.
The most important part of this is the manifest configuration. Second, we are going to create executable and classpath-aware jar, with the link to the dependencies copied in the first step: Ĭom. In our case, we'll create a folder named libs inside the project build directory (which is usually the target folder). First, we specify the goal copy-dependencies, which tells Maven to copy these dependencies into the specified outputDirectory.
0 kommentar(er)
