I’ve compiled a maven-on web application, now the war can be downloaded to any web server, and everything is successful (1). But in maven, it is also possible to automatically start the server using mvn compile tomcat:run , for example (2).

In the first case, the application does not configure the server, i.e. it turns out the customer (let's say) will have to configure it himself before launch.

And in the second situation, the web application is tightly bound to some server, which is also not good, and you also need to have a maven.

So, how to act in such cases?

    2 answers 2

    tomcat:run is usually not for the application to be launched by the customer, but for the convenience of the developer.

    To give the war is quite normal.

      The distribution kit with your application (set of files in the archive \ installer) + documentation with comprehensive information on the project is given to the customer. In what format? - agreed with the customer, or if he is passive - then at your discretion.

      Maven is only needed by the developer, except when you have an extension system and in the documentation you tell how to write those extensions to your software (what dependencies to connect to maven, etc.).