Executing mvn verify deploy will execute the build lifecycle twice. No need to do that. Just execute mvn deploy as the deploy phase comes after the verify phase. Clean phase is of different lifecycle though. So in your case: mvn clean deploy
However, there might be a bug nevertheless as your execution shouldn't typically generate an exception. /Anders (mobile) On Aug 5, 2016 18:19, <org.apache.maven.u...@io7m.com> wrote: Hello. I've run into a bizarre problem when trying to deploy a project. If I run "mvn clean verify", the project builds without issue. If I run "mvn clean verify deploy", the project fails to build (on the very last module, naturally). The error is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (default-jar) on project io7m-jsx-tests: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] I am not attaching supplemental artifacts in that module, and am also not replacing any. The project in question is here: https://github.com/io7m/jsx/tree/develop The failure occurs when deploying the io7m-jsx-tests module: http://ataxia.io7m.com/2016/08/05/build.txt Note that there are no sources in src/main as this is a module containing the unit tests for all other modules. However, this has not been a problem to date and have used this arrangement without issue in some 40 or so projects. Today, it suddenly appears to be a problem. Is this a bug? Is there anything I can do to fix it? M
