I just noticed that this mostly replicates what is offered as jakarta-servlet (javax + jakarta namespace) already offers, but with slightly different OSGi metadata (e.g. it requires java 11) what leads to some subtile dependency problems here:
as there is not really any description in the repository itself I wonder what is the purpose of offering the same API again that seems to be available else-where?
Should it matter what API bundle/jar is actually used with jetty? Is it for historic reasons?
I just noticed that this mostly replicates what is offered as
jakarta-servlet(javax + jakarta namespace) already offers, but with slightly different OSGi metadata (e.g. it requires java 11) what leads to some subtile dependency problems here:as there is not really any description in the repository itself I wonder what is the purpose of offering the same API again that seems to be available else-where?
Should it matter what API bundle/jar is actually used with jetty? Is it for historic reasons?