On 07/17/2013 09:21 PM, Simone Caronni wrote: > Hello, > > I'm experiencing differences between "mvn" and "mvn-rpmbuild". With "mvn" > the project builds fine; while I have the following error when using > "mvn-rpmbuild": > > [...] > DEBUG: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:attached (make-zip) on > project guacamole-common-js: Assembly is incorrectly configured: null: > Assembly is incorrectly configured: null: > DEBUG: [ERROR] Assembly: null is not configured correctly: Assembly ID must > be present and non-empty. This is answered in Maven Assembly Plugin FAQ: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#required-classifiers In short, assembly ID is missing. You need to add it to Assembly Descriptor. > > The project submodule contains the correct Assembly ID: > > <build> > > <plugins> > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptors> > <descriptor>static.xml</descriptor> > </descriptors> > </configuration> > <executions> > <execution> > <id>make-zip</id> > <phase>package</phase> > <goals> > <goal>attached</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > > </build> This looks like fragment of POM. Assembly ID is part of Assembly Descriptor, not Project Object Model. > > The only way I've found so far to build the project is to patch away the > guacamole-common-js module from the build. Can someone explain me what > should I do? Patching assembly descriptor should help: sed -i '/<assembly>/a\ <id>foo</id>' src/main/assembly/static.xml Alternatively add <appendAssemblyId>false</appendAssemblyId> to plugin configuration (recommended in the FAQ, but not by me). -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
