https://issues.apache.org/bugzilla/show_bug.cgi?id=57199
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
tomcat-embed-core requires exactly one of either tomcat-embed-logging-juli or
tomcat-embed-logging-log4j. This was true before the change to add
WebappProperties.
The change to add WebappProperties has triggered failures at compile time if no
logging dependency is present but there always would have been failures at
runtime (unless a very strange sub-set of functionality was used).
Given that we can't express the dependency we want to express in the pom, the
aim has been to identify the least worst work-around. Given that we need Jasper
and WebSocket to depend on core and to remain optional, I don't see a better
solution right now.
Possibilities I've considered:
1. Create core+juli and core+log4j
Just moves the problem to which should Jasper/WebSocket depend on?
Creates a new issue for folks that want to use their own JULI impl hard-coded
to their favourite logging framework.
2. Create X+noJuli, X+Juli, X+log4j for each of core, jasper, websocket with
appropriate dependencies between them.
Fixes the issue but doubles the number of packages and raises a number of
questions about how to package them for download. My feeling is that this would
create more problems than it solves.
Absent a better idea I'm leaning towards resolving this as WONTFIX.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
