maven-jetty-plugin

Cryptic jetty-maven-plugin error message 'ERROR: PWC6117: File “null” not found'

前提是你 提交于 2019-12-01 06:33:24
I have a Maven Webapp producing a WAR file. I've just upgraded my Jetty plugin to the 7.4.2.v20110526 (from 6.x). I have the following set up: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>7.4.2.v20110526</version> <executions> <execution> <id>jetty-run</id> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> <connectors> <connector implementation="${connector}"> <port>80</port> <maxIdleTime>60000</maxIdleTime> </connector> </connectors> <webAppConfig> <contextPath>/foo</contextPath> </webAppConfig> <webappDirectory>$

Cryptic jetty-maven-plugin error message 'ERROR: PWC6117: File “null” not found'

风流意气都作罢 提交于 2019-12-01 05:18:38
问题 I have a Maven Webapp producing a WAR file. I've just upgraded my Jetty plugin to the 7.4.2.v20110526 (from 6.x). I have the following set up: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>7.4.2.v20110526</version> <executions> <execution> <id>jetty-run</id> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> <connectors> <connector implementation="${connector}"> <port>80</port> <maxIdleTime>60000</maxIdleTime> <

How to cancel start or shutdown jetty if WebAppContext fails to start

三世轮回 提交于 2019-12-01 01:37:15
问题 I am using Maven Jetty Plugin, is there a way to prevent the server from starting up or shutting down (for example with maven-jetty-plugin) if ANY bean fails? Here's an example: 2013-04-22 11:43:59.327:WARN:oejw.WebAppContext:main: Failed startup of context o.e.j.m.p.JettyWebAppContext@9a681a{/,file:/opt/bamboo/bamboo-home/xml-data/build-dir/APA-BC-JETTYAPA/src/main/webapp/,STARTING}{file:/opt/bamboo/bamboo-home/xml-data/build-dir/APA-BC-JETTYAPA/src/main/webapp/} org.springframework.beans

File upload working under Jetty but not under Tomcat

佐手、 提交于 2019-11-30 22:44:46
I have a web application with spring in which I do some file upload. Under eclipse, using Jetty (the maven plugin) it works perfectly. But when I deploy the application under Tomcat it does not and I get the following Exception : org.springframework.web.bind.MissingServletRequestParameterException: Required org.springframework.web.multipart.MultipartFile parameter 'file' is not present org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter$ServletHandlerMethodInvoker.raiseMissingParameterException(AnnotationMethodHandlerAdapter.java:545) org.springframework.web.bind

Enable debug logging in maven jetty 7 plugin

守給你的承諾、 提交于 2019-11-30 08:14:38
I'm running a java webapp with a simple mvn jetty:run , using the latest jetty plugin, but I can't seem to find a way to tell jetty to output DEBUG messages to console (for the embedded jetty instance, not the plugin itself). It's currently outputting only WARN and INFO messages. I've tried setting -DDEBUG and -DVERBOSE , but they don't do anything. I've already had a look at the documentation , but it doesn't seem to cover this. Update: OK, I finally got things working and here is what I did. My understanding is that Jetty 7 doesn't have any dependencies on a particular logging framework,

No plugin found for prefix 'jetty' in the current project

放肆的年华 提交于 2019-11-30 07:59:28
I have added jetty mvn plugin code in my project pom.xml. <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.26</version> <configuration> <contextPath>/redkites</contextPath> </configuration> <executions> <execution> <id>start-jetty</id> <phase>deploy</phase> <goals> <goal>run</goal> </goals> <configuration> <scanIntervalSeconds>10</scanIntervalSeconds> <daemon>true</daemon> </configuration> </execution> </executions> </plugin> When I use commands sudo mvn compile and sudo mvn clean install , I didn't find any errors & build successfully, but

Change Jetty default port

隐身守侯 提交于 2019-11-30 04:46:23
Jetty default port is 8080, but I want to change to default port to some other port (9999). I read a few tutorials and they said almost all of configuration information is by default maintained in file jetty.xml , this file is located under $JETTY_HOME/etc/ . Then, change property jetty.port to 9999. However, when I opened up that file, I couldn't find jetty.port property inside the jetty.xml . I'm currently using Jetty-9.2.1 and the port is at 8080. I found jetty.port property under jetty-http.xml file. Even though I changed the port to 8090 in the jetty-http.xml file, jetty is still running

Maven: How to use jetty:run in a multi-module Maven project, without needing to install

故事扮演 提交于 2019-11-30 04:39:43
I'm new to Maven. I have a multi-module maven 2 project that has the following structure (somewhat simplified): Project (POM packaging) | +-- Module1 (JAR) | | | +-- src | | | +-- main | | | +-- java | +-- resources | +-- Module2 (JAR) | | | ... | +-- Web Module (WAR) | ... I've configured the Web Module to include the Maven Jetty plugin . This works great for building the production artifacts. For development, I discovered that I need to call mvn install on any module that I change, followed by stoping jetty and calling jetty:run again. It would be much more productive if there was a way for

jetty-env.xml with DataSource leads to failing WebAppContext on mvn jetty:run

*爱你&永不变心* 提交于 2019-11-29 19:35:39
问题 I have a really simple webapp project with maven and jetty that has been working very well until now. But now I need to setup MySQL connection pooling with JNDI as the database connections always time out. First of all here is the relevant content of my pom.xml: <modelVersion>4.0.0</modelVersion> ... <packaging>war</packaging> ... <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <jetty-version>8.1.0.v20120127</jetty-version> </properties> <dependencies> ...

Enable debug logging in maven jetty 7 plugin

天大地大妈咪最大 提交于 2019-11-29 11:21:23
问题 I'm running a java webapp with a simple mvn jetty:run , using the latest jetty plugin, but I can't seem to find a way to tell jetty to output DEBUG messages to console (for the embedded jetty instance, not the plugin itself). It's currently outputting only WARN and INFO messages. I've tried setting -DDEBUG and -DVERBOSE , but they don't do anything. I've already had a look at the documentation, but it doesn't seem to cover this. 回答1: Update: OK, I finally got things working and here is what I