Solution: mvn org.mortbay.jetty:maven-jetty-plugin:run-war
The following is all nonsense!
Environment: Intellig IEDA + MAVEN build!
For novices, BUG is commonplace. Here is a record of the errors encountered when using maven:
Error 1: Enter the command mvn jetty : Error when running:
[ERROR] No plugin found for prefix’jetty’ in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/kongyin02/.m2/repository), dianping- internal-snapshots (http://mvn.dianpingoa.com/dianping-snapshots), dianping-internal-releases (http://mvn.dianpingoa.com/dianping-releases), dianping-central-cache (http:// mvn.dianpingoa.com/third-party), central (http://mvn.dianpingoa.com/dprepo), local-snapshot-plugin-repository (http://maven.sankuai.com/nexus/content/groups/ public-snapshots), local-plugin-repository (http://maven.sankuai.com/nexus/content/groups/public)] ->[Help 1]
Solution 1: Just add the following node to the maven setting.xml file:
<pluginGroups> <pluginGroup>org.mortbay.jettypluginGroup> pluginGroups>
My setting.xml file is placed in the .m2 folder of the maven run folder.
Solution 2:If you don’t want to add extra The node can be started by the following command:
mvn org.mortbay.jetty:maven-jetty- plugin:run
But here, you will find another New ERROR (what??), Don’t worry, look down:
It means: The project does not meet MAVEN’s standards. But if you don’t want to modify this structure (especially for novices, I don’t dare to change it at all, otherwise I don’t need to eat lunch, maybe dinner is also free…), what should I do?
Solution:
Use: jetty:run-war< /p>
The original jetty:run-war will package the application by default, and then execute the deployment ${ project.build.directory}/${project.build.finalName}.war. Just modify the position of the webApp:
<configuration>
webApp >${basedir}/target/mycustom.war webApp > configuration <pluginGroups> << span style="color:rgb(128,0,0)">pluginGroup>org.mortbay.jettypluginGroup> pluginGroups>
My setting.xml file is placed in the .m2 folder of the maven run folder.
mvn org.mortbay.jetty:maven- jetty-plugin:run
But here, you will find another New ERROR (what??), Don’t worry, look down:
It means: the project does not meet MAVEN standards. But if you don't want to modify this structure (especially for novices, I don't dare to change it at all, otherwise I don't need to eat lunch, maybe dinner is also free...), what should I do?
Solution:
Use: jetty:run-war< /p>
The original jetty:run-war will package the application by default, and then execute the deployment ${ project.build.directory}/${project.build.finalName}.war. Just modify the position of the webApp:
<configuration>
webApp >${basedir}/target/mycustom.war webApp > configuration < we bApp >${basedir}/target/mycustom.war webApp >
configuration
< p>So the final solution is:
mvn org.mortbay.jetty:maven-jetty-plugin:run -war