¡Ü °³¹ßÇÑ ¶óÀ̺귯¸® jar ¸¦ »ç¼³ ·¹Æ÷ÁöÅ丮¿¡ deploy ÇÏ·Á°í mvn deploy:deploy ¸í·É ¼öÇà½Ã ¿À·ù ¹ß»ý.
The packaging for this project did not assign a file to the build artifact.
¡Ü ÇØ°á ¹æ¹ý
"mvn deploy:deploy" ¸í·É ´ë½Å "mvn deploy" ¸í·ÉÀ» ½ÇÇàÇØ¾ß ÇÕ´Ï´Ù.
"mvn deploy" ¸í·ÉÀº Äڵ带 ÄÄÆÄÀÏÇÏ°í jar ·Î ÆÐŰ¡ÇÑ ÈÄ, ¿ø°Ý ·¹Æ÷ÁöÅ丮¿¡ µðÇ÷ÎÀÌ(deploy) ÇÕ´Ï´Ù.
¹Ý¸é, "mvn deploy:deploy" ¸í·ÉÀº maven-deploy-plugin ÀÇ deploy °ñ(goal)¸¸À» ¼öÇàÇÕ´Ï´Ù.
"mvn deploy:deploy" ¸í·ÉÀ¸·Î´Â ¾ÆƼÆåÆ®(artifact; jar ÆÄÀÏ)¸¦ »ý¼ºÇÏ´Â ¶óÀÌÇÁ »çÀÌŬ ´Ü°è°¡ ¾ø±â ¶§¹®¿¡
µðÇ÷ÎÀÌ ÇÒ jar ÆÄÀÏÀ» ãÀ» ¼ö ¾ø°Ô µÇ¹Ç·Î "The packaging for this project did not assign a file to the build artifact." ¿¡·¯¸¦
¹ß»ýÇÏ°í Á¾·áÇÏ°Ô µË´Ï´Ù.
ÀÌ ³»¿ëÀº maven-deploy-plugin ÀÇ FAQ ¿¡µµ µî·ÏµÇ¾î ÀÖ½À´Ï´Ù.
https://maven.apache.org/plugins/maven-deploy-plugin/faq.html#deploy_deploy
¡Ü ¿ø¹®
You need to run "mvn deploy" instead of "mvn deploy:deploy".
The former executes the maven lifecycle up to the "deploy" phase,
i.e. it compiles your code, packages it into a JAR file and finally deploys it to your remote repository.
"mvn deploy:deploy" on the other hand does only execute the deploy goal of the maven-deploy-plugin.
Without the context of the previously executed lifecycle phases,
which produce your actual build artifact (the JAR file),
the maven-deploy-plugin does not have anything to deploy and aborts with the error
The packaging for this project did not assign a file to the build artifact.
This behavior is also explained in the FAQ of the maven-deploy-plugin.
|