Open joakime opened 2 years ago
Having an IT test project that currently is not able to show output, being configured to show output would be a great first start. It should be a war project that has something that will prevent proper initialization of the webapp. This kind of error should be presented to the user.
See changes from PR #8106 for details on discussion, and what changes made there need review.
The jetty-maven-plugin since we changed jetty to use the slf4j-api has only 2 ways to define the jetty logger implementation:
<dependencies>
(this effectively puts the slf4j impl on the container classpath)<modules>
It is not correct to add a <dependency>
to the webapp to solve a container classpath problem.
I'm fairly sure the majority of the plugin it tests will show output, however there may be 1 or 2 that are not configured properly - identifying and fixing those would be useful for diagnosing it test failures.
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.
Jetty version(s) 12
Java version/vendor
(use: java -version)
17Description
Two things have been noticed when working with the tests against the
jetty-ee#-maven-plugin
implementations in Jetty 12.First, is that there seems to be no way to show output.
You'll get ...
I have not found a configuration of a
<packaging>war</packaging>
project that uses thejetty-ee#-maven-plugin
that will allow output to show.And secondly, is the
ELContextCleaner
triggers exceptions ...