maven-jetty-plugin

Context and setup information: Jetty 9 with the eclipse jetty plugin Spring 4.1.1.RELEASE with Spring Security 3.2.3 Spring Java Configuration (no web.xml) Problem description Starting jetty 9 is very slow in a project where Spring's JavaConfig is used to boot the Spring context instead of using a web.xml . Jetty seems to be doing nothing during a considerate amount of time. This occurs after the line: INFO:oejs.Server:main: jetty-9.2.3.v20140905 Jetty does start eventually, but takes very long to start up compared to a regular tomcat 7 distribution. Additional resources public class

I'm using maven-jetty-plugin and trying to override my jetty.xml setting with the -Djetty.port=8090 but it's not working. Only when I remove the connector part from the jetty.xml file I get the port to be 8090. So: mvn jetty:run -Djetty.port=8090 With the connector starts in port 8080 Without the connector starts in port 8090 Problem is I need to configure acceptors, stats and other stuff. I tried removing only the port from the connector but it didn't work. I'm using: JAVA 1.7_05 MAVEN 3.0.4 Jetty 8.1.4 Linux Ubuntu 12.04 64bits Here's my pom.xml plugin configuration: <plugin> <groupId>org

I have an XML file (urlrewrite.xml) that needs a property placeholder resolved. I enable Maven filtering to achieve this. This works fine for the assembled WAR file. <build> <resources> <resource> <directory>src/main/resources</directory> <filtering>true</filtering> </resource> The problem is when trying to run the application in development mode using the maven-jetty-plugin (Maven Jetty Plugin), as maven jetty:run . The file in question, urlrewrite.xml, is located in the src/main/resources directory, and therefore should (and does) ends up in /WEB-INF/classes (or target/classes for maven

I have a Spring Roo project and I use mvn jetty:run to run my app. The only problem is changes to the *.java classes do not hot deploy, while changes to *.jspx hot deploy fine. So how can I configure mvn jetty to hotdeploy for java classes? You need to set the scanIntervalSeconds to a value greater than 0 to enable it: scanIntervalSeconds - The interval in seconds to scan the webapp for changes and restart the context if necessary. Ignored if reload is enabled. Disabled by default. Default value is : 0. So the configuration might looks like this: <plugin> <groupId>org.mortbay.jetty</groupId>

I'm trying to split a Maven WAR project into two modules, so that I can build a separate JAR file with command line tools. The result has the following structure: pom.xml (packaging pom , has two modules) project-jar/ pom.xml (packaging jar ) project-war/ pom.xml (packaging war , depends on project-jar ) If I run mvn commands from the root, everything works fine. I'd like to keep using mvn jetty:run , but for that I need to execute the command in the WAR subproject. If I do that, fails to find the project-jar subproject, so it won't run. Even mvn jetty:run-war with a completely assembled WAR

I'm trying to get around the common issue of Jetty locking static files on Windows with the technique of setting useFileMappedBuffer to false in webdefault.xml. Unfortunately, every time Jetty is not picking up my customized webdefault.xml. I'm using Apache Maven 3.0.2. I've tried using the maven-jetty-plugin (v6.1.26) and jetty-maven-plugin (v8.0.0.M2) but with no difference. I've tried running clean and rebuilding as well before running Jetty. I've verified each time that my webdefault.xml was taken from the same version as the plugin and has the correct settings, namely, only changing this

This question already has an answer here: Set default home page via <welcome-file> in JSF project 3 answers Accessing http://localhost:8080/basicSetup/faces/index.xhtml works, with the output of : Hello World ! Albert Kam but accessing http://localhost:8080/basicSetup shows Hello World ! #{myBean.value} meaning that the welcome file is not rendered as a JSF file I would like http://localhost:8080/basicSetup to have the same effect as accessing http://localhost:8080/basicSetup/faces/index.xhtml . Please share your thoughts jetty-maven-plugin:8.0.3.v20111011:run + jdk 7 + eclipse indigo Here is