Re: How about javax to jakarta migration in Storm?

2023-09-28 Thread Richard Zowalla
Hi,

yes, the coordinate move came with EE9, although EE8 will still be around some 
day.

It will require to update Jetty _and_ check transient dependencies for 
compatibility. I didn't check but it might be that some auth libs (from hadoop) 
might rely on javax dependencies causing issues at runtime.

Nothing against a Jira to track.

Gruß
Richard 



Am 28. September 2023 15:34:36 MESZ schrieb Alexandre Vermeerbergen 
:
>Hello,
>
>I noticed we still rely on javax.servlet in storm-server/pom.xml.
>
>Unless I am missing something, Java EE" APIs are supposed to be
>deprecated in favor in Jakarta EE APIs.
>
>While I don't know the scope of needed changes in Storm to move to
>Jakarta EE APIs, is there any objection if I create a JIRA to track
>such change (potentially needing Jettty update, etc) ?
>
>Having a look to https://issues.apache.org/jira/browse/STORM-3961, I
>see that Richard had this topic in mind, but I found no STORM JIRA
>explicitly meaning "Upgrade to Jarkarta EE APIs"
>
>Thanks,
>Alexandre


How about javax to jakarta migration in Storm?

2023-09-28 Thread Alexandre Vermeerbergen
Hello,

I noticed we still rely on javax.servlet in storm-server/pom.xml.

Unless I am missing something, Java EE" APIs are supposed to be
deprecated in favor in Jakarta EE APIs.

While I don't know the scope of needed changes in Storm to move to
Jakarta EE APIs, is there any objection if I create a JIRA to track
such change (potentially needing Jettty update, etc) ?

Having a look to https://issues.apache.org/jira/browse/STORM-3961, I
see that Richard had this topic in mind, but I found no STORM JIRA
explicitly meaning "Upgrade to Jarkarta EE APIs"

Thanks,
Alexandre