| Summary: | Jetty debug turned on by default | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Felis Cattus <feles> |
| Component: | osgi | Assignee: | Hugues Malphettes <hmalphettes> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gregw, jetty-inbox |
| Version: | unspecified | ||
| Target Milestone: | 7.1.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Felis Cattus
Probably related to the issue: When "Validate Plug-ins" is invoked on the run configuration for the application, the following problem is displayed: org.slf4j.api Missing Constraint: Require-Capability: generic; filter="(&(generic=org.slf4j.impl.StaticLoggerBinder)(&(generic=org.slf4j.impl.StaticLoggerBinder)(&(generic=org.slf4j.impl.StaticLoggerBinder)(&(version>=1.5.5)(!(version>=1.5.12))))))" I'm not sure the first line can be turned off without setting up the logger specially - but the debugs should not be there unless debug is turned on switching this to osgi component This is affecting the jetty-6 version with the packaging of jetty made by equinox. Also comment #2 shows an installation specific issue: equinox uses commons-logging I beleive and when jetty is used within a set of equinox features, I think the logging framework is correctly setup. Felis do you still have the issue? We can help you with some general knowledge about commons-logging, slf4j in equinox, equinox and and how jetty-6 is packaged there. I don't see these debugs any more, thank you. |