Maven The packaging for this project did not assign a file to the build artifact

Question

I m using Maven 3 0 3 on Mac 10 6 6   I have a JAR project and when I run the command  mvn clean install install   I m getting the error     ERROR  Failed to execute goal org apache maven plugins maven-install-plugin 2 3 1 install  default-cli  on project StarTeamCollisionUtil  The packaging for this project did not assign a file to the build artifact - gt   Help 1    What does this mean and how can I fix it   Below is my pom xml   Let me know what other info would be helpful and I ll edit this post   Thanks  - Dave   lt 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 xsd maven-4 0 0 xsd  gt   lt modelVersion gt 4 0 0 lt  modelVersion gt   lt groupId gt com myco starteam util lt  groupId gt   lt artifactId gt StarTeamCollisionUtil lt  artifactId gt   lt packaging gt jar lt  packaging gt   lt name gt StarTeam Collision Util lt  name gt   lt description gt      The StarTeam Collision Utility provides developers and release engineers alike the ability to     compare files attached to a set of CRs to see if conflicts exist in the change set   lt  description gt   lt version gt 1 0-SNAPSHOT lt  version gt   lt url gt http   cm-build myco com 8080 hudson view Tools job StarTeamCollisionUtil - TRUNK  lt  url gt   lt properties gt       lt project build sourceEncoding gt UTF-8 lt  project build sourceEncoding gt   lt  properties gt   lt repositories gt       lt repository gt           lt id gt myco-sonatype-nexus-snapshots lt  id gt           lt name gt MyCo Sonatype-Nexus Snapshots lt  name gt           lt url gt http   sonatype myco com nexus content repositories snapshots  lt  url gt       lt  repository gt   lt  repositories gt   lt dependencies gt       lt dependency gt           lt groupId gt starteam lt  groupId gt           lt artifactId gt starteam lt  artifactId gt           lt version gt 1 1 0 lt  version gt           lt type gt jar lt  type gt           lt scope gt system lt  scope gt           lt systemPath gt   basedir  lib starteam110 jar lt  systemPath gt       lt  dependency gt       lt dependency gt           lt groupId gt junit lt  groupId gt           lt artifactId gt junit lt  artifactId gt           lt version gt 4 8 2 lt  version gt       lt  dependency gt       lt dependency gt           lt groupId gt org apache ant lt  groupId gt           lt artifactId gt ant lt  artifactId gt           lt version gt 1 8 1 lt  version gt       lt  dependency gt       lt dependency gt           lt groupId gt javax mail lt  groupId gt           lt artifactId gt mail lt  artifactId gt           lt version gt 1 4 1 lt  version gt           lt type gt jar lt  type gt           lt scope gt compile lt  scope gt       lt  dependency gt   lt  dependencies gt   lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt version gt 2 8 1 lt  version gt           lt  plugin gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-site-plugin lt  artifactId gt               lt version gt 3 0-beta-3 lt  version gt               lt configuration gt                   lt reportPlugins gt                       lt plugin gt                           lt groupId gt org apache maven plugins lt  groupId gt                           lt artifactId gt maven-surefire-report-plugin lt  artifactId gt                           lt version gt 2 5 lt  version gt                       lt  plugin gt                       lt plugin gt                           lt groupId gt org apache maven plugins lt  groupId gt                           lt artifactId gt maven-javadoc-plugin lt  artifactId gt                           lt version gt 2 7 lt  version gt                           lt configuration gt                               lt linksource gt true lt  linksource gt                           lt  configuration gt                       lt  plugin gt                       lt plugin gt                           lt groupId gt org apache maven plugins lt  groupId gt                           lt artifactId gt maven-jxr-plugin lt  artifactId gt                           lt version gt 2 2 lt  version gt                       lt  plugin gt                       lt plugin gt                           lt groupId gt org codehaus mojo lt  groupId gt                           lt artifactId gt versions-maven-plugin lt  artifactId gt                           lt version gt 1 2 lt  version gt                       lt  plugin gt                       lt plugin gt                           lt groupId gt org apache maven plugins lt  groupId gt                           lt artifactId gt maven-project-info-reports-plugin lt  artifactId gt                           lt version gt 2 3 1 lt  version gt                           lt reportSets gt                               lt reportSet gt                                   lt reports gt                                       lt report gt index lt  report gt                                       lt report gt dependencies lt  report gt                                       lt report gt dependency-management lt  report gt                                       lt report gt cim lt  report gt                                       lt report gt issue-tracking lt  report gt                                       lt report gt license lt  report gt                                       lt report gt scm lt  report gt                                   lt  reports gt                               lt  reportSet gt                           lt  reportSets gt                       lt  plugin gt                   lt  reportPlugins gt               lt  configuration gt           lt  plugin gt       lt  plugins gt   lt  build gt   lt distributionManagement gt       lt repository gt           lt id gt sonatype-nexus lt  id gt           lt url gt http   sonatype myco com nexus content repositories snapshots  lt  url gt       lt  repository gt   lt  distributionManagement gt   lt scm gt       lt url gt https   starteam cmass myco com BorlandStarTeam BorlandStarTeam jsp lt  url gt   lt  scm gt   lt issueManagement gt       lt system gt StarTeam lt  system gt       lt url gt https   starteam cmass myco com BorlandStarTeam BorlandStarTeam jsp lt  url gt   lt  issueManagement gt   lt ciManagement gt       lt system gt Hudson lt  system gt       lt url gt http   cm-build myco com 8080 hudson  lt  url gt   lt  ciManagement gt   lt  project gt

User · Accepted Answer

I don t know if this is the answer or not but it might lead you in the right direction     The command install install is actually a goal on the maven-install-plugin  This is different than the install maven lifecycle phase   Maven lifecycle phases are steps in a build which certain plugins can bind themselves to  Many different goals from different plugins may execute when you invoke a single lifecycle phase    What this boils down to is the command     mvn clean install   is different from     mvn clean install install   The former will run all goals in every cycle leading up to and including the install  like compile  package  test  etc    The latter will not even compile or package your code  it will just run that one goal  This kinda makes sense  looking at the exception  it talks about      StarTeamCollisionUtil  The packaging for this project did not assign a file to the build artifact   Try the former and your error might just go away

User · Answer

I have same issue   Error message for me is not complete  But in my case  I ve added generation jar with sources  By placing this code in pom xml     lt build gt        lt pluginManagement gt           lt plugins gt               lt plugin gt                   lt artifactId gt maven-source-plugin lt  artifactId gt                   lt version gt 2 1 2 lt  version gt                   lt executions gt                       lt execution gt                           lt phase gt deploy lt  phase gt                           lt goals gt                               lt goal gt jar lt  goal gt                           lt  goals gt                       lt  execution gt                   lt  executions gt               lt  plugin gt           lt  plugins gt       lt  pluginManagement gt   lt  build gt    So in deploy phase I execute source jar goal which produces jar with sources  And deploy ends with BUILD SUCCESS

User · Answer

you must clear the target file such as in jar and others In C  drive your folder at  m2 see the location where it install and delete the  jar file Snaphot file and delete target files then clean the application you found it will be run

User · Answer

I have seen this error occur when the plugins that are needed are not specifically mentioned in the pom  So mvn clean install  will give the exception if this is not added       lt plugin gt           lt groupId gt org apache maven plugins lt  groupId gt           lt artifactId gt maven-install-plugin lt  artifactId gt           lt version gt 2 5 2 lt  version gt    lt  plugin gt   Likewise  mvn clean install deploy  will fail on the same exception if something like this is not added   lt plugin gt      lt artifactId gt maven-deploy-plugin lt  artifactId gt      lt version gt 2 8 1 lt  version gt      lt executions gt         lt execution gt            lt id gt default-deploy lt  id gt            lt phase gt deploy lt  phase gt            lt goals gt               lt goal gt deploy lt  goal gt            lt  goals gt         lt  execution gt      lt  executions gt   lt  plugin gt   It makes sense  but a clearer error message would be welcome

User · Answer

TL DR To fix this issue  invoke packaging plugin before  e g  for jar packaging use maven-jar-plugin   as following   mvn jar jar install install   Or   mvn jar jar deploy deploy    If you actually needed to deploy   Gotcha This approach won t work if you have multi-module project with different packagings  ear war jar zip   ndash  even worse  wrong artifacts will be installed deployed  In such case use reactor options to only build the deployable module  e g  the war      Explanation  In some cases you actually want to run directly a install install or deploy deploy goal  that is  from the maven-deploy-plugin  the deploy goal  not the Maven deploy phase  and you would end up in the annoying The packaging for this project did not assign a file to the build artifact   A classic example is a CI job  a Jenkins or Bamboo job  e g   where in different steps you want to execute care about different aspects    A first step would be a mvn clean install  performing tests and test coverage A second step would be a Sonarqube analysis based on a quality profile  e g  mvn sonar sonar plus further options Then  and only after successful tests execution and quality gate passed  you want to deploy to your Maven enterprise repository the final project artifacts  yet you don t want to re-run mvn deploy  because it would again execute previous phases  and compile  test  etc   and you want your build to be effective but yet fast    Yes  you could speed up this last step at least skipping tests  compilation and execution  via -Dmaven test skip true  or play with a particular profile  to skip as many plugins as possible   but it is much easier and clear to simply run mvn deploy deploy then   But it would fail with the error above  because as also specified by the plugin FAQ      During the packaging-phase all gathered and placed in context  With this mechanism Maven can ensure that the maven-install-plugin and maven-deploy-plugin are copying uploading the same set of files  So when you only execute deploy deploy  then there are no files put in the context and there is nothing to deploy    Indeed  the deploy deploy needs some runtime information placed in the build context by previous phases  or previous plugins goals executions    It has also reported as a potential bug  MDEPLOY-158  deploy deploy does not work for only Deploying artifact to Maven Remote repo    But then rejected as not a problem   The deployAtEnd configuration option of the maven-deploy-plugin won t help neither in certain scenarios because we have intermediate job steps to execute      Whether every project should be deployed during its own deploy-phase or at the end of the multimodule build  If set to true and the build fails  none of the reactor projects is deployed   experimental    So  how to fix it  Simply run the following in such a similar third last step   mvn jar jar deploy deploy   The maven-jar-plugin will not re-create any jar as part of your build  thanks to its forceCreation option set to false by default      Require the jar plugin to build a new JAR even if none of the contents appear to have changed  By default  this plugin looks to see if the output jar exists and inputs have not changed  If these conditions are true  the plugin skips creation of the jar    But it will nicely populate the build context for us and make deploy deploy happy  No tests to skip  no profiles to add  Just what you need  speed     Additional note  if you are using the build-helper-maven-plugin  buildnumber-maven-plugin or any other similar plugin to generate meta-data later on used by the maven-jar-plugin  e g  entries for the Manifest file   you most probably have executions linked to the validate phase and you still want to have them during the jar jar build step  and yet keep a fast execution   In this case the almost harmless overhead is to invoke the validate phase as following   mvn validate jar jar deploy deploy     Yet another additional note  if you have not jar but  say  war packaging  use war war before install deploy instead   Gotcha as pointed out above  check behavior in multi module projects

User · Answer

While  A Di-Matteo answer does work for non multimodule I have a solution for multimodules   The solution is to override every plugin configuration so that it binds to the phase of none with the exception of the jar war ear plugin and of course the deploy plugin  Even if you do have a single module my rudimentary tests show this to be a little faster  for reasons I don t know  performance wise   Thus the trick is to make a profile that does the above that is activated when you only want to deploy   Below is an example from one of my projects which uses the shade plugin and thus I had to re-override the jar plugin not to overwrite        lt profile gt         lt id gt deploy lt  id gt         lt activation gt           lt property gt             lt name gt buildStep lt  name gt             lt value gt deploy lt  value gt           lt  property gt         lt  activation gt         lt build gt           lt plugins gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default-compile lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt                 lt execution gt                   lt id gt default-testCompile lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt                 lt execution gt                   lt id gt test-compile lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt               lt  executions gt             lt  plugin gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-surefire-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default-test lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt               lt  executions gt             lt  plugin gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-install-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default-install lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt               lt  executions gt             lt  plugin gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-resources-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default-resources lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt                 lt execution gt                   lt id gt default-testResources lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt               lt  executions gt             lt  plugin gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-shade-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default lt  id gt                   lt phase gt none lt  phase gt                 lt  execution gt               lt  executions gt             lt  plugin gt             lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-jar-plugin lt  artifactId gt               lt executions gt                 lt execution gt                   lt id gt default-jar lt  id gt                   lt configuration gt                     lt forceCreation gt false lt  forceCreation gt                   lt  configuration gt                 lt  execution gt               lt  executions gt             lt  plugin gt           lt  plugins gt         lt  build gt       lt  profile gt    Now if I run mvn deploy -Pdeploy it will only run the jar and deploy plugins   How you can figure out which plugins you need to override is to run deploy and look at the log to see which plugins are running  Make sure to keep track of the id of the plugin configuration which is parens after the name of the plugin

User · Answer

This error shows up when using the maven-install-plugin version 3 0 0-M1  or similar   As already mentioned above and also here the following plug-in version works        lt plugin gt           lt groupId gt org apache maven plugins lt  groupId gt           lt artifactId gt maven-install-plugin lt  artifactId gt           lt version gt 2 5 2 lt  version gt       lt  plugin gt

User · Answer

This worked for me when I got the same error message    mvn install deploy

User · Answer

This reply is on a very old question to help others facing this issue    I face this failed error while I were working on my Java project using IntelliJ IDEA IDE   Failed to execute goal org apache maven plugins maven-install-plugin 2 4 install  default-cli  on project getpassword  The packaging for this project did not assign a file to the build artifact   this failed happens  when I choose install install under Plugins - install  as pointed with red arrow in below image     Once I run the selected install under Lifecycle as illustrated above  the issue gone  and my maven install compile build successfully

User · Answer

I had the same issue but I executed mvn install initially  not install install as it was mentioned earlier    The solution is to include     lt plugin gt           lt groupId gt org apache maven plugins lt  groupId gt           lt artifactId gt maven-install-plugin lt  artifactId gt           lt version gt 2 5 2 lt  version gt    lt  plugin gt    Into plugin management section

[maven] Maven: The packaging for this project did not assign a file to the build artifact

Examples related to maven

Examples related to maven-3

Examples related to pom.xml

Examples related to maven-jar-plugin

Examples related to maven-install-plugin