Failed To Create Assembly Error Adding File
Contents |
here for a quick overview of the site failed to create assembly error adding file to archive Help Center Detailed answers to any questions you might
Failed To Create Assembly You Must Set At Least One File
have Meta Discuss the workings and policies of this site About Us Learn failed to create assembly error adding file isn't a file more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Error Reading Assemblies: No Assembly Descriptors Found
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up maven-assembly-plugin MojoExecutionException with dependencySet as outputDirectory up vote 8 down vote mojoexecutionexception in maven favorite 1 In my Khatami project I'm using maven to both manage compilation and package up the result into a runnable artifact: executable shell-script at the top-level, bin/ containing the executable jar and its dependent jars. Please see what I mean here. For reference, here's the salient part of Khatami's pom.xml:
cannot
Maven Assembly Plugin Example
work with m2eclipse 0.9.7Agile Board ExportXMLWordPrintableJSON Details maven-shade-plugin Type: Improvement Status: Closed Priority: Major Resolution: Won't Fix Affects Version/s: 2.2-beta-2 http://stackoverflow.com/questions/6737221/maven-assembly-plugin-mojoexecutionexception-with-dependencyset-as-outputdirecto Fix Version/s: None Component/s: None Labels: None Environment: Eclipse 3.4.1, m2eclipse 0.9.7, maven-assembly-plugin 2.2-beta-2 Description After upgrading to m2eclipse 0.9.7 my assembly goal stopped working: https://issues.apache.org/jira/browse/MASSEMBLY-396 [DEBUG] Adding 68 dependency artifacts. [DEBUG] Adding artifact: net.tipp24.argo.procurement:procurement-common:jar:0.1.0-SNAPSHOT with file: /home/ckutz/procurement/eclipse_ws/argo-procurement/procurement-common/target/classes to assembly location: libs/procurement-common-0.1.0-SNAPSHOT.jar. [DEBUG] Adding file: /home/ckutz/procurement/eclipse_ws/argo-procurement/procurement-common/target/classes to archive location: procurement-server-0.1.0-SNAPSHOT/libs/procurement-common-0.1.0-SNAPSHOT.jar [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to create assembly: Error adding file 'net.tipp24.argo.procurement:procurement-common:jar:0.1.0-SNAPSHOT' to archive: /home/ckutz/procurement/eclipse_ws/argo-procurement/procurement-common/target/classes isn't a file. [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error adding file 'net.tipp24.argo.procurement:procurement-common:jar:0.1.0-SNAPSHOT' to archive: /home/ckutz/procurement/eclipse_ws/argo-procurement/procurement-common/target/classes isn't a file. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.
Sign in Pricing Blog Support Search GitHub This repository Watch 394 Star 4,041 Fork 823 thinkaurelius/titan Code https://github.com/thinkaurelius/titan/issues/411 Issues 129 Pull requests 37 Projects 0 Wiki Pulse Graphs http://blog.soebes.de/blog/2013/09/28/build-smells-maven-assembly-plugin New issue Configure Maven to build JDK 6 artifacts and assemblies #411 Closed dalaro opened this Issue Oct 5, 2013 · 3 comments Projects None yet Labels None yet Milestone titan0.4 Assignees dalaro 3 participants Aurelius member dalaro failed to commented Oct 5, 2013 In addition to the JDK 7 artifacts and assemblies built by default dalaro was assigned Oct 5, 2013 dalaro referenced this issue in thinkaurelius/faunus Oct 5, 2013 Open Configure Maven to build JDK 6 artifacts and assemblies #150 karkumar commented Oct 10, 2013 Hi I'm trying to use the failed to create -Pjre6 target and I am running into this error: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble-standalone-dir) on project titan-dist-all: Failed to create assembly: Error adding file 'com.thinkaurelius.titan:titan-core:jar:0.4.0-SNAPSHOT' to archive: /Users/myusername/Sandbox/titan/titan/titan-core/target/classes isn't a file. -> [Help 1] [ERROR] Aurelius member dalaro commented Oct 11, 2013 Hi, Use -Dtargetjre=6 instead of -Pjre6. Just specifying -Pjre6 does not disable the jre7 profile that is enabled by default. $ mvn -N help:active-profiles -Pjre6 [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Titan: Distributed Graph Database 0.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ titan --- [INFO] Active Profiles for Project 'com.thinkaurelius.titan:titan:pom:0.4.0-SNAPSHOT': The following profiles are active: - jre6 (source: com.thinkaurelius.titan:titan:0.4.0-SNAPSHOT) - jre7 (source: com.thinkaurelius.titan:titan:0.4.0-SNAPSHOT) Compare: $ mvn -N help:active-profiles -Dtargetjre=6 [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Titan: Distributed Graph Database 0.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @ titan --- [INFO] Active Profiles for Project 'com.thinkaurelius.titan:titan:pom:0.4.0-SNAPSHOT': The following profiles are active: - jre6 (source: com.thinkaurelius.titan:
you are a software developer (for example in Java) you might have heard about code smells which indicate not really bugs, but usually are a kind of indicator for problems in the future. It´s usually a good practice to fix such code smells. But sometimes if I take a deeper look into a Maven build I can observe things like Build Smells which could produce problems in future but not need to. So the best practice for Code Smells as well as Build Smells is to fix such things as soon as possible. Let us start with simple example on the first glance. The Distribution It´s often the case that you like to create a kind of distribution package which contains the created artifacts. Apart from that it is sometimes also usefull having supplemental files into such distribution packages as well. The Obvious Solution Let us assume having two modules which you like to package into the final zip distribution archive. This will bring you to use the maven-assembly-plugin with an appropriate assembly descriptor like this: Assembly Descriptor 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25