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

by

I don’t know if this is the answer or not but it might lead you in the right direction…

(I believe these steps are for people working with Intellij IDE. The install:install is available in the Maven panel on the right by default. The below steps are alternative to it.)

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!

More Related Contents:

  1. Maven: Lifecycle vs. Phase vs. Plugin vs. Goal [closed]
  2. Maven Out of Memory Build Failure
  3. Is effective-pom a merge between super pom and application POM
  4. Maven Could not resolve dependencies, artifacts could not be resolved
  5. How to disable maven blocking external HTTP repositories?
  6. How can I include test classes into Maven jar and execute them?
  7. How to override maven property in command line?
  8. Error when deploying an artifact in Nexus
  9. Remove or delete resource files from target directory using pom file
  10. How does maven sort version numbers?
  11. Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved
  12. Maven check for updated dependencies in repository
  13. Intellij idea cannot resolve anything in maven
  14. Maven – Depend on assembled zip
  15. Verification of dependency authenticity in Maven POM based automated build systems
  16. Maven 3 warnings about build.plugins.plugin.version
  17. How to share a common build.gradle via a repository?
  18. maven 3: Accessing version of “root” corporate POM
  19. What is the difference in Maven between dependency and plugin tags in pom.xml?
  20. How do I force Maven to use my local repository rather than going out to remote repos to retrieve artifacts?
  21. How to access maven.build.timestamp for resource filtering
  22. Is there a way to exclude a Maven dependency globally?
  23. How do you stop maven from trying to access http://repo.maven.apache.org?
  24. Where is super pom for maven 3?
  25. Warning on using project.parent.version as the version of a module in Maven 3
  26. Finding the root directory of a multi module Maven reactor project
  27. Maven build issue – Connection to repository refused
  28. How to override the `project.build.finalName` Maven property from the command line?
  29. How to exclude maven dependencies?
  30. How to pass java code a parameter from maven for testing

Leave a Comment