Honestly, this may turn out to be an issue with IntelliJ rather than this extension but just wanted to share:
My team recently began using this extension and had no problems with it. But when I tried it out personally, it didn't work. I consistently got java.net.BindException: Address already in use at some point when doing mvn clean install. To clarify: this is on a multi-module maven project, so even with the extension, we expect the servlet container to turn on once per module, so a few times. The error suggests that a Tomcat from the previous suite did not shut down properly and it failed the suite of the next module.
After some time, we figured out I'm the only one who runs Maven goals via the Intellij GUI, and the rest do plain mvn commands on the command line. When I ran it from the terminal, everything was fine.
The difference in how IntelliJ invokes maven seems to be key and wanted to document this.
Honestly, this may turn out to be an issue with IntelliJ rather than this extension but just wanted to share:
My team recently began using this extension and had no problems with it. But when I tried it out personally, it didn't work. I consistently got
java.net.BindException: Address already in useat some point when doingmvn clean install. To clarify: this is on a multi-module maven project, so even with the extension, we expect the servlet container to turn on once per module, so a few times. The error suggests that a Tomcat from the previous suite did not shut down properly and it failed the suite of the next module.After some time, we figured out I'm the only one who runs Maven goals via the Intellij GUI, and the rest do plain mvn commands on the command line. When I ran it from the terminal, everything was fine.
The difference in how IntelliJ invokes maven seems to be key and wanted to document this.