Maven deploy: packaging for this project did not assign a file to an assembly artifact

Question

I am trying to deploy a maven project to a remote repository.

mvn install works great for a local repository.

I use Groovy and the Groovy compiler plugin -Eclipse. I tried running mvn deploy to deploy to a remote repository, and I got the following error:

The packaging for this project did not assign a file to the build artifact -> [Help 1] 

This is my pom.xml:

 <project> <modelVersion>4.0.0</modelVersion> <groupId>io.github.notacariocafacil</groupId> <artifactId>notacariocafacil</artifactId> <version>1.0</version> <packaging>jar</packaging> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.10</version> </dependency> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>1.8.6</version> </dependency> </dependencies> <build> <extensions> <extension> <groupId>org.kuali.maven.wagons</groupId> <artifactId>maven-s3-wagon</artifactId> <version>1.2.1</version> </extension> </extensions> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.5.1</version> <configuration> <compilerId>groovy-eclipse-compiler</compilerId> <source>1.6</source> <target>1.6</target> </configuration> <dependencies> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-eclipse-batch</artifactId> <version>1.8.6-01</version> </dependency> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-eclipse-compiler</artifactId> <version>2.7.0-01</version> </dependency> </dependencies> </plugin> <plugin> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-eclipse-compiler</artifactId> <version>2.7.0-01</version> <extensions>true</extensions> </plugin> </plugins> </build> </project> 

Do I need to add something at the build stage?

Answer 1

You need to run mvn deploy instead of mvn deploy:deploy . The first executes the maven lifecycle right up to the “deployment” phase, that is, compiles your code, packs it into a JAR file, and finally deploys it to your remote repository.

mvn deploy:deploy , on the other hand, runs only the deploy command for maven-deploy-plugin. Without the context of the previously completed lifecycle steps that produce your actual build artifact (JAR file), maven-deploy-plugin has nothing to deploy and abort with error The packaging for this project did not assign a file to the build artifact . This behavior is also explained in the maven-deploy-plugin FAQ .