maven-assembly-plugin

问题 I am trying use regular expression in maven-assembly-plugin which is shown below. There are files with the names starts with ABC502. I am trying to copy only the rpms with the 3 or 4 in suffix. Below one is not working. rpm names are given below ABC5023-buildnumber.rpm ABC5024-buildnumber.rpm ABC5025-buildnumber.rpm ABC5026-buildnumber.rpm <fileSet> <directory>${project.build.directory}/tar_content/stackcontents/</directory> <outputDirectory>scripts/data/rpms/</outputDirectory> <includes>

问题 In Eclipse, you can create a project jar with its required dependencies in an adjacent sub-folder by doing ... Export->Java->Runnable JAR file Select Library handling option: Copy required libraries into a sub-folder next to the generated JAR Is there a way to do this with the Maven assembly plugin? Or is there another Maven plugin that would be more appropriate for this task? Thanks! 回答1: yes you can use assembly plugin. pom.xml: <build> <!-- final name set the jar name, if left it will give

问题 I'm sorry to sound ignorant here, but I'm new to Maven, and have been banging my head against something that I'm sure is quite simple. The docs say: [...] a project could produce a ZIP assembly which contains a project's JAR artifact in the root directory, the runtime dependencies in a lib/ directory, and a shell script to launch a stand-alone application. which is exactly what I want to do! But I can't seem to make it happen. My POM is as follows: <project> <modelVersion>4.0.0</modelVersion>

问题 I have a project which has dependency A. Project is packing into WAR and dependency A - into jar. And another dependency B, which also depends on A. I want to pack project and when project B is packing it must rebuild its dependency A instead of getting compiled dependency. Please help, how can i achieve this 回答1: Always perform a clean when doing an install, ie mvn clean install . This will make sure that all modules in the project are rebuilt, packaged, and installed in the local .m2

问题 I have a project which has dependency A. Project is packing into WAR and dependency A - into jar. And another dependency B, which also depends on A. I want to pack project and when project B is packing it must rebuild its dependency A instead of getting compiled dependency. Please help, how can i achieve this 回答1: Always perform a clean when doing an install, ie mvn clean install . This will make sure that all modules in the project are rebuilt, packaged, and installed in the local .m2

问题 I am new to maven and spent ~3 days in generating the zip file with assembly plugin refering to http://www.petrikainulainen.net/programming/tips-and-tricks/creating-a-runnable-binary-distribution-with-maven-assembly-plugin/ My project is multi module, so I also referred to Managing multi-module dependencies with Maven assembly plugin Still I have several inefficiencies. Below is assembly.xml (which I inherited from 1st link) <assembly> <id>bin</id> <!-- Generates a zip package containing the

问题 We use Hudson and the maven-release-plugin to do the release builds. Now I have a project which contains an assembly that puts together all needed components and then packages them into a .tar.gz package with the desired directory structure. Now I'm trying to get the release-plugin to deploy this package to our Maven repository during the release:perform goal, but only the standard stuff (sources, javadoc, POM) are deployed. I've already bound the assembly goal to the maven package phase, and

问题 I am trying to add an obfuscation step while packaging my app. I supposed that I had to insert the Proguard plugin between the compiler plugin and the assembly (the assembly just put all of my app and dependencies into one single jar). <build> <finalName>myApp</finalName> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.2</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin>

问题 I am trying to compile a maven project, the source code uses Generics and other featuers of Java 1.5, thus causing my build to fail In my POM.xml I have configured the build configuration against 1.5 for the source and target properties, but this doesn't solve my issue Is my POM.xml correct, or am I missing something? Thanks <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http:/

问题 This is my pom file: <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"> <modelVersion>4.0.0</modelVersion> <groupId>com.sia.g7</groupId> <artifactId>sia</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>sia</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>log4j</groupId> <artifactId