maven-assembly-plugin

I'm having a problem with this very redundant maven configuration. The application I'm working on sometimes gets built for environments that need alternate resource bundles. The current way the resources are prepared for deployment is that they are added to a single .zip file. The build master then deploys the zipped resources to the server. For some environments, alternate versions of some of the resources need to be used. The folder structure in the project looks like this: src/main/resources - resource1 - resource2 - resource2 ENV1/ -resource1 (environment-specific) ENV2/ -resource1

I dont get any error with this code. Just that the file that I want to exclude still gets added. I am using the maven plugin for eclipse <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <id>only</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> <archive> <manifest> <mainClass>com.Main</mainClass> </manifest> </archive> <descriptorRefs> <descriptorRef>jar-with-dependencies</descriptorRef> </descriptorRefs> <excludes> <exclude>**/com/uiservices/controllers/*.* </exclude> </excludes> </configuration> </execution> </executions> <

I have a multi-module project and want to create a single jar containing the classes of all my modules. Inside my parent POM, I declared the following plugin: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <configuration> <descriptorRefs> <descriptorRef>bin</descriptorRef> </descriptorRefs> </configuration> </plugin> However, when running mvn assembly:assembly, only the source from the parent folder (empty) are included. How do I include the sources from my modules into the archive? I think you are looking for the Maven Shade Plugin: http:/

TL;DR When some (specific) transitive dependencies are excluded in the POM file but the assembly descriptor is set to fetch all dependencies , the excluded dependencies will be included in assembly. How can I prevent this? A bit of background Some dependencies may be tricky to handle because their groupIds and artifactIds change at almost each version (in my case, bouncycastle). I am retrieving several versions of bouncycastle (138, 1.38, 1.45 and 1.50). My purpose is to eliminate all versions other than 1.50. To be precise, I have one dependency (let's call it some.perfectly.done:job ) which

I get Error reading assemblies: No assembly descriptors found when building my project. I'm trying to set permissions for my .sh files and exclude a nasty .jar file that makes my application crash...I don't think the problem is about that though.... My maven-assembly plugin is added like this in my pom.xml file: <plugin> <artifactId>maven-assembly-plugin</artifactId> <version>2.2.1</version> <executions> <execution> <id>make-assembly</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> <descriptors> <descriptor>src/main/assembly/src.xml</descriptor> </descriptors> <

Maven's assembly plugin enables the creation of a big jar including all dependencies with descriptorRef jar-with-dependencies . How can one exclude some of these dependencies? It seems like it does not have such a configuration? Is there another solution? Raghuram This example indicates one way to do this: <dependencySets> <dependencySet> .... <excludes> <exclude>commons-lang:commons-lang</exclude> <exclude>log4j:log4j</exclude> </excludes> </dependencySet> .... </dependencySets> Essentially we would use the excludes option available in dependencySet . See also: https://maven.apache.org

I'm starting to work with Maven but am not yet successfully thinking in Maven's terms. I have a specific requirement and the docs aren't giving me enough clues, so I could use a bit of help: I'd like to create an assembly that builds a jar-with-dependencies like the "standard" target of this name, but excluding a couple of the resources. I want log4j.properties and a couple of other configuration files to not be in the jar. builds a .ZIP file containing in its root directory the .jar from step 1 as well as the above mentioned config files. I want to fire this assembly up from the command line

Similar question here . I would like to get ONE resulting WAR to be deployed from 3 different maven modules. The war modules are absolutely non-conflicting : First one that has Java classes and some WEB-INF/artifacts Second one are just API - interfaces - that must be either already present in container or part of the resulting war (that's what I want) Third one with Implementation classes, WEB-INF/artifacts ( spring infrastructure, web.xml, etc) First one depends on interfaces and implementation. Third one depends on the interfaces. I have a total mess in possible options. Do I use Overlays