Right, this was the intention to be able to run http.base with Servlet
API 6.
I fixed the package import and started a new release, 5.1.16 should be
available in a few days.
Regards
Carsten
On 04.06.2025 08:23, Kolhoff, Jacqueline - ENCOWAY wrote:
Hi Carsten,
Thank you very much for your response and your explanations regarding the
changes.
Since we have an automated update process that regularly checks for newer patch
versions of our dependencies, we would keep running into this issue otherwise.
So it would definitely help if the package import were reverted to [6.0,7).
Especially since http.base ā if Iām interpreting the code changes correctly ā
can still handle Servlet API 6.0.
Regards,
Jacqueline.
________________________________
Von: Carsten Ziegeler <cziege...@apache.org>
Gesendet: Mittwoch, 4. Juni 2025 06:33 Uhr
An: users@felix.apache.org <users@felix.apache.org>
Betreff: Re: Unexpected Jakarta Servlet 6.1.0 dependency in
org.apache.felix.http.base 5.1.14
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi,
the implementation change in http.base is a minor addition but I also
agree that the version should have increased at least on the minor version.
We didn't spot this as all the usage of http.base we have is embedding
that jar inside another bundle and then the imports are handled on that
level.
Would it help, if we change the package import back to [6.0,7) ?
Regards
Carsten
On 02.06.2025 10:48, Kolhoff, Jacqueline - ENCOWAY wrote:
Hello,
we are using org.apache.felix.http.base and wanted to upgrade from version 5.1.12 to
5.1.14 in order to stay up to date. Unfortunately, our application no longer runs with
this version, because it now includes jakarta.servlet-api 6.1.0, and as a result, the
MANIFEST.MF now imports the package jakarta.servlet;version="[6.1,7)".
However, our application is still running in a Jakarta EE 10 environment
(Servlet API 6.0 and Tomcat 10.1). We were wondering why increasing the patch
version of org.apache.felix.http.base from 5.1.12 to 5.1.14 introduces such a
significant change? Shouldn't this have been released as a major version
instead?
Regards, Jacqueline.
--
Carsten Ziegeler
Adobe
cziege...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
--
Carsten Ziegeler
Adobe
cziege...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org