Re: [jetty-users] Completely different behaviour when using maven jetty

[Jan Bartel <janb@xxxxxxxxxxx>]

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 <saadmaz@xxxxxxxxxxx> 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
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

--

Jan Bartel <janb@xxxxxxxxxxx>

www.webtide.com
Expert assistance from the creators of Jetty and CometD