For the record. I fixed the jenkins issue by running a shell script that invokes the maven command instead of running that maven command in Jenkins. That solved it, which sounds like buggy jenkins behaviour to me.
-- View this message in context: http://jetty.4.n6.nabble.com/Forked-Jetty-complete-logging-tp4959482p4959527.html Sent from the Jetty User mailing list archive at Nabble.com. _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
