[MAGNOLIA-6913] Servlets 3.0 upgrade Created: 04/Jan/17  Updated: 20/Feb/17  Resolved: 19/Jan/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5, 5.5.1
Fix Version/s: 5.5.2

Type: Epic Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLCE-57 Update web.xml to Servlet 3.0. Closed
dependency
is depended upon by MGNLPN-250 Visitor cookie - not possible to make... Closed
Template:
Epic Name: Servlets 3.0 upgrade
Acceptance criteria:
Empty
Date of First Response:
Sprint: Basel 79
Story Points: 21

 Description   

While investing MGNLPN-250 where I need the upgrade to Servlets 3.0, I noticed we currently have a version discrepancy between pom.xml and web.xml. This ticket is about updating the dependency in main, and in all others modules, as sadly the artifactId has changed from servlet-api to javax.servlet-api.

To keep dependencies in sync, we are also upgrading javax.servlet.jsp-api version (as well as artifactId) to 2.2.1.



 Comments   
Comment by Mikaël Geljić [ 06/Jan/17 ]

I pushed additional commits on that PR; essentially updating version and coordinates of jsp-api (2.2.1) according to the EE 6 baseline too; jstl isn't relocated (as per Mr. Burns' post, back when Java EE 6 API artifacts got deployed to maven central)

We should do that one too for the downstream modules, agree? (Not even sure why the UI even has jsp-api as a dep anywhere, but it has).

EDIT: description was already updated

Generated at Mon Feb 12 04:19:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.