install error -- The packaging for this project did not assign a file to the build artifact

[Dave Alvarado]

Hi,

I'm using Maven 3.0.3. I'm trying to run the install plugin (using "install:install") to install my WAR file to my local repo. However, I'm getting an error, shown below. As far as I can tell, my pom.xml file is set up correctly. I have also included it.

davea-mbp2:socialmediaproxy davea$ mvn install:install
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building socialmediaproxy 0.1
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-cli) @ socialmediaproxy ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.071s
[INFO] Finished at: Wed Apr 13 14:23:21 CDT 2011
[INFO] Final Memory: 9M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-cli) on project socialmediaproxy: The packaging for this project did not assign a file to the build artifact -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Thanks for any advice, - Dave


<?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://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>socialmediaproxy</groupId> <artifactId>socialmediaproxy</artifactId> <packaging>war</packaging> <version>0.1</version> <scm> <developerConnection>scm:git:http://mydomain.com/socialmediaproxy.git</developerConnection> </scm> <dependencies> <dependency> <groupId>org.grails</groupId> <artifactId>grails-crud</artifactId> <version>1.2.1</version> </dependency> <dependency> <groupId>org.grails</groupId> <artifactId>grails-gorm</artifactId> <version>1.2.1</version> </dependency> <!-- Grails defaults to Ehache for the second-level Hibernate cache. --> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-ehcache</artifactId> <version>3.3.1.GA</version> </dependency> <dependency> <groupId>net.sf.ehcache</groupId> <artifactId>ehcache-core</artifactId> <version>1.7.1</version> <exclusions> <exclusion> <groupId>net.sf.ehcache</groupId> <artifactId>jms</artifactId> </exclusion> <exclusion> <groupId>net.sf.ehcache</groupId> <artifactId>servlet-api</artifactId> </exclusion> <!-- We have JCL-over-SLF4J instead. --> <exclusion> <groupId>net.sf.ehcache</groupId> <artifactId>commons-logging</artifactId> </exclusion> </exclusions> </dependency> <!-- For ease of development and testing, we include the HSQLDB database. --> <dependency> <groupId>hsqldb</groupId> <artifactId>hsqldb</artifactId> <version>1.8.0.10</version> </dependency> <!-- Use Log4J for logging. This artifact also pulls in the Log4J JAR. --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.8</version> <scope>runtime</scope> </dependency> <dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> <version>1.2</version> </dependency> </dependencies> <repositories> <!-- Required to get hold of JTA --> <repository> <id>maven2-repository.dev.java.net</id> <name>Java.net Repository for Maven</name> <url>http://download.java.net/maven/2/</url> <layout>default</layout> </repository> <repository> <id>Codehaus Snapshots</id> <url>http://snapshots.repository.codehaus.org</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>Codehaus Snapshots</id> <url>http://snapshots.repository.codehaus.org</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </pluginRepository> </pluginRepositories> <build> <pluginManagement /> <plugins> <plugin> <groupId>org.grails</groupId> <artifactId>grails-maven-plugin</artifactId> <version>1.3.4</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>init</goal> <goal>maven-clean</goal> <goal>validate</goal> <goal>config-directories</goal> <goal>maven-compile</goal> <goal>maven-test</goal> <goal>maven-war</goal> <goal>maven-functional-test</goal> </goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-scm-plugin</artifactId> <version>1.5</version> <configuration> <goals>install</goals> <username>username</username> <password>password</password> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.2</version> <configuration> <artifactItems> <artifactItem> <groupId>${project.groupId}</groupId> <artifactId>${project.artifactId}</artifactId> <version>${project.version}</version> <type>${project.packaging}</type> <overWrite>true</overWrite> <outputDirectory>${warDestinationDir}</outputDirectory> </artifactItem> </artifactItems> </configuration> </plugin> </plugins> </build> <profiles> <profile> <id>tools</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>${java.version}</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> <!-- destination deployment directories --> <profile> <id>dev</id> <properties> <warDestinationDir>/Library/Tomcat/Home/webapps</warDestinationDir> </properties> </profile> <profile> <id>test</id> <properties> <warDestinationDir>/Library/Tomcat/Home/webapps</warDestinationDir> </properties> </profile> </profiles> </project>

[Peter Johnson]

Try running "mvn install" instead.

If you run "mvn install", then Maven performs all of the build phases for a war (the packaging type) up through the install phase.

If you run "mvn install:install", Maven runs only the install goal of the Install plugin. That is, the other build phases are not run. And it is the compile phase that assigns a file (the war file) to the build artifact. Since the compile phase doesn't run it you give install:install as the goal, then Maven complains about "did not assign a file to the build artifact.

I you don't want to run the whole build, use the install:install-file goal instead.

[Dave Alvarado]

Hi Peter, Thanks for that explanation. This command

mvn install:install-file -Dfile=target/socialmediaproxy-0.1.war -DgroupId=socialmediaproxy -DartifactId=socialmediaproxy -Dpackaging=war -Dversion=0.1

indeed works. However I have a follow-up. It seems redundant to me to respecify my groupId, artifactId, packaging, and version since those are all in my pom.xml file. Is there a way I can rewrite the command above so that what is deployed is what is in my pom.xml file?

Thanks, - Dave