Open sbordet opened 1 week ago
@sbordet The module system already supports a [deprecated]
mechanism that adds a (deprecated)
label in module lists and warns if a deprecated module is enabled.
Currently it is only used in jetty-home/src/main/resources/modules/logging-log4j1.mod
, so maybe this issue should be used to use it more widely?
Jetty version(s) 12.1.x
Enhancement Description Jetty module may need to be deprecated, for example due to renamings, or because features are not supported anymore, or they were experimental, or the classes used have been deprecated.
Would be great to add a deprecation mechanism.
Perhaps would be enough to add "deprecated" to the
[tags]
directive, and emit a log that the module is deprecated, similarly to what we do with XML properties.Or perhaps a full blown
[deprecated]
directive with indications about what is the replacement, since when, etc.