nvim-wildcat icon indicating copy to clipboard operation
nvim-wildcat copied to clipboard

[Wildcat]  Error executing 'mvn clean package'. Run Maven manually to get more info.

Open egolep opened this issue 2 years ago • 4 comments

In the last days I started to have this error everytime I try to use WildcatRun. Nothing has changed in my environment.

There is a way to see a log from Wildcat?

egolep avatar Dec 04 '23 14:12 egolep

In the last days I started to have this error everytime I try to use WildcatRun. Nothing has changed in my environment.

There is a way to see a log from Wildcat?

Hi, @egolep When you get "Error executing 'mvn clean package'. Run Maven manually to get more info." means that your build with maven has compile errors, so Wildcat can't run with and ungenerated war. If you run manually "mvn clean package", does maven execute it correctly?

javiorfo avatar Dec 04 '23 14:12 javiorfo

Sorry, I should have specified that. Yeah, when I run mvn clean package from the command line for the same exact project, I get no compilation errors. I tried both to use an anaconda environment (what I've been using since now) and system packages to see if something changes, but it doesn't. I'm on Manjaro Linux, using Tomcat 8.5.87 and openjdk version 8.0.382 and maven version 3.9.5

egolep avatar Dec 04 '23 14:12 egolep

The command :WildcatRun builds your project with "mvn clean package", copies the generated war into the server (Tomcat in your case) and starts the server.

To spot the error, please execute these phases separately:

  • Run "mvn clean package"
  • Execute the command :WildcatDeploy (this copies the generated war into the server)
  • Execute the command :WildcatInfo (to make sure Tomcat is set as default and the war has been copied)
  • Execute :WildcatUp to start the server

If any of these instructions fail, I will be easier to spot the problem

javiorfo avatar Dec 04 '23 14:12 javiorfo

I tried all of these steps and none failed. However, the application is not correctly deployed, since I get a 404 when I try to go to the corresponding URL (aka localhost:8080/application-name/).

egolep avatar Dec 04 '23 14:12 egolep