Sorry Jan: smazahir-mac:jaxrs smazahir$ mvn -v Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T12:39:06-07:00) Maven home: /usr/local/Cellar/maven/3.5.0/libexec Java version: 1.8.0_131, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
Unfortunately, addding maven logging seems equivalent to the '-X' flag and results in a working server. The full debug out is pretty large. For comparison: Successfully launches jetty server with mvn clean install jetty:run (no other code change): https://pastebin.com/qFVcd7r4 [https://pastebin.com/i/facebook.png]<https://pastebin.com/qFVcd7r4> Succesfully running jetty server (without changes) - Pastebin.com<https://pastebin.com/qFVcd7r4> pastebin.com Failed to launch with just mvn clean install jetty:run (has my pom change) -- https://pastebin.com/8gfkA2qD [https://pastebin.com/i/facebook.png]<https://pastebin.com/8gfkA2qD> Failed jetty server to launch - Pastebin.com<https://pastebin.com/8gfkA2qD> pastebin.com The debug output is very large and difficult to share. My intent was to compare a debug output with my change and one without, but since the one with my change somehow succeeds when run with the debug flag I'm a bit stuck. Doing a simple diff shows there is a lot of noise in the diff (e.g. timestamps) and nothing obvious. ________________________________ From: [email protected] <[email protected]> on behalf of Jan Bartel <[email protected]> Sent: October 17, 2018 12:42 AM To: JETTY user mailing list Subject: Re: [jetty-users] Completely different behaviour when using maven jetty plugin with and without debug flag Hi, You didn't mention the version of jetty, the version of java, the version of maven, nor the os you're running on, so that makes it more difficult to help you. To help pinpoint the problem, you could edit the $MAVEN_HOME/conf/logging/simplelogger.properties file, and turn on all jetty debug logging by adding a line like: org.slf4j.simpleLogger.log.org.eclipse.jetty=DEBUG Compare the output you get with/without the -X option. Jan On Wed, 17 Oct 2018 at 15:21, Saad Mazahir <[email protected]<mailto:[email protected]>> wrote: Hi all, I have a jetty server which runs fine normally. When I try to add a new POM dependency, the war file fails to get assembled. When I run the plugin but with the debug switch enabled, the war file get's assembled and run's fine. That is: Bad: mvn clean install jetty:run mvn clean install jetty:run -Dorg.eclipse.jetty.annotations.maxWait=420 webAppSourceDirectory/Users/smazahir/Workspace/zodiac/touchless_maven_fix/simpleServer/jaxrs/target/swagger-jaxrs-server-1.0.0 does not exist. Good: mvn clean install jetty:run -Dorg.eclipse.jetty.annotations.maxWait=420 -X What could cause this discrepancy? How can I debug whether adding a new pom dependency actually causes my project to fail? Thanks. _______________________________________________ jetty-users mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel <[email protected]<mailto:[email protected]>> www.webtide.com<http://www.webtide.com> Expert assistance from the creators of Jetty and CometD
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
