limit jetty scanning in maven plugin
java,eclipse,maven,jetty,maven-jetty-plugin
This is what I use for my projects to speed up Jetty startup just from the maven pom.xml file (no external configuration is required): <plugin> <groupId>org.eclipse.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <configuration> <webApp> <!-- no need to scan anything as we're using servlet 2.5 and moreover, we're not using ServletContainerInitializer(s) --> <!-- for more...
Can I do maven jetty restart on change of spring xmls?
java,maven,spring-mvc,intellij-idea,maven-jetty-plugin
Thanks @peeskillet. When I added the follwoing, it started working. <scanTargetPatterns> <scanTargetPattern> <directory>src/main/webapp</directory> <includes> <include>**/*.xml</include> </includes> </scanTargetPattern> </scanTargetPatterns> I had to switch the window to make it working....
Jetty maven plugin and spring 4.1.6 - class not found exception
java,spring,maven,jetty,maven-jetty-plugin
Where's your spring-context-4.1.6.RELEASE.jar ? The org.springframework.context.ApplicationContextException class is found in that jar....
How do I get deploy-war to work using jetty 9 maven plugin?
jetty,maven-jetty-plugin,jetty-9
The documentation you linked to tells you why. Set the daemon parameter to false and it will block...
optional block in jelly.config not translating to the backend in jenkins plugin development.
java,jenkins,jenkins-plugins,maven-jetty-plugin,jelly
In your created job, what does the XML have? You can get this from the URL localhost:8080/job//config.xml I would guess that you need a doFillOperatingSystemItems call like here untested public ListBoxModel doFillOperatingSystemItems( @QueryParameter String operatingSystem ) { return new ListBoxModel( new Option("rhel", "rhel", operatingSystem.matches("rhel") ), new Option("linux", "linux", operatingSystem.matches("linux") )...
Cannot run jetty-maven-plugin in windows 7
java,eclipse,maven,jetty,maven-jetty-plugin
If you check in stack-trace, You could find the following error message. Which means different jdks are used in compile and run time. Please check the jdk versions Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/jetty/maven/plugi n/JettyRunMojo : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) ...
No plugin found for prefix 'jetty' in the current project
maven,jetty,maven-jetty-plugin
You may need to add org.mortbay.jetty to the list of groupIds looked up by default. So edit your ${user.home}/.m2/settings.xml accordingly: <pluginGroups> <!-- your existing plugin groups if any --> ... <pluginGroup>org.mortbay.jetty</pluginGroup> </pluginGroups> Quoting the Shortening the Command Line section of the plugin development guide, ... add your plugin's groupId to...
Webapp hangs when Active MQ broker is running
spring,jms,activemq,maven-jetty-plugin,jstack
I found the cause of the issue and was able to fix it: we were passing a transactionmanager to the AbstractMessageListenerContainer. While in production there is a XA-Transactionmanager in use on the local jetty environment only a JPATransactionManager is used. Apparently the JMS is waiting forever for an XA transaction...
Connection properties error when starting JBoss as a Maven plugin
java,maven,jboss,maven-jetty-plugin
which version of maven you use? Try a maven version 3.0.x :) and it will work! what are the maven commands you use? try: mvn clean install -Pall mvn jboss:start mvn jetty:run-all best regards Rene...
How to run Jetty with JRebel in Eclipse?
maven,jetty,embedded-jetty,maven-jetty-plugin,jrebel
I have luckily found the answer in the Maven configuration page (where i call jetty:run) and it works. For those who will also need this and use the JRebel Eclipse plugin, here is the answer: (I would still be appreciated if someone knows a better way. Maybe in pom.xml, in...
meaning of leading slash(“/”) in spring-mvc return statement
maven,spring-mvc,tomcat,path,maven-jetty-plugin
With this type of mapping the return value represents a view name, and to reason properly about the delimeters you have to consider the configuration of your ViewResolverInstance, the view URL is being assembled as view.setUrl(getPrefix() + viewName + getSuffix()); so if you have e.g. <beans:bean class="org.springframework.web.servlet.view.InternalResourceViewResolver"> <beans:property name="prefix" value="/WEB-INF/views/"...
Inexplicably unresolvable IncompatibleClassChangeError in jetty-maven-plugin with Spring
java,spring,maven,jetty,maven-jetty-plugin
I took a look at your pom using mvn dependency:tree. You have a mix of Spring 3.2 and 3.1 JARs. The Spring 3.2 JARs are being pulled in by Restlet. [INFO] +- org.restlet.jee:org.restlet:jar:2.3.1:compile [INFO] +- org.restlet.jee:org.restlet.ext.servlet:jar:2.3.1:compile [INFO] +- org.restlet.jee:org.restlet.ext.spring:jar:2.3.1:compile [INFO] | +- cglib:cglib-nodep:jar:2.2:compile [INFO] | +- commons-logging:commons-logging:jar:1.1.3:compile [INFO] | +-...
Servlet - requestDispatcher.forward java.lang.NullPointerException
jsp,servlets,nullpointerexception,maven-jetty-plugin,requestdispatcher
Talk about overcomplicating things... here I was thinking something was off about the two consecutive calls to the same page by the doGet and the doPost, that maybe the response or the request might had got an attribute corrupted or something, or even worse the config was buggy... nope, as...
java.lang.ClassNotFoundException: org.mortbay.jetty.plus.naming.Resource
java,jetty,zk,maven-jetty-plugin
i resolved the problem by using the version 7.0.0pre2 of jetty-maven-plugin and jsp-2.1 as follow : <properties> <jetty.version>7.0.0pre2</jetty.version> </properties> <dependencies> <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>jsp-2.1</artifactId> <version>${jetty.version}</version> </dependency> </dependencies> <build> <finalName>${project.artifactId}</finalName> <plugins> <plugin>...
Jrebel - ERROR org.zeroturnaround.bundled.javassist.CannotCompileException: [source error] no such class: classCache
java,spring,maven-jetty-plugin,jrebel
Updating to the latest version fixed the problem it seems there is an issue with the 5.5 version of jrebel and now I am using the latest 6.2.1 Release build and the errors are gone. Solution is to Download the latest standalone version of Jrebel and configure the jrebel.jar in...