I'm using Maven 3.0.3. I'm trying to run the install plugin (using "install:install") to install my WAR file to my local repo. However, I'm getting an error, shown below. As far as I can tell, my pom.xml file is set up correctly. I have also included it.
If you run "mvn install", then Maven performs all of the build phases for a war (the packaging type) up through the install phase.
If you run "mvn install:install", Maven runs only the install goal of the Install plugin. That is, the other build phases are not run. And it is the compile phase that assigns a file (the war file) to the build artifact. Since the compile phase doesn't run it you give install:install as the goal, then Maven complains about "did not assign a file to the build artifact.
I you don't want to run the whole build, use the install:install-file goal instead.
Hi Peter, Thanks for that explanation. This command
indeed works. However I have a follow-up. It seems redundant to me to respecify my groupId, artifactId, packaging, and version since those are all in my pom.xml file. Is there a way I can rewrite the command above so that what is deployed is what is in my pom.xml file?
Thanks, - Dave
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: install error -- The packaging for this project did not assign a file to the build artifact