[
https://issues.apache.org/jira/browse/VELTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867072#comment-17867072
]
Michael Osipov commented on VELTOOLS-202:
-----------------------------------------
[~cbrisson], I wouldn't be too fast about it. There are pros and cons in this
case. One of the biggest problems is that you need to supply source and javadoc
JARs for that which will be hard. In general, classifiers are side artifacts
and not the main artifact. Classifiers of classifiers? No! Here we have main
source code with another namespace. More over, how to do testing?
One possible solution is another artifact with copies the code and replaces the
relevant parts. E.g.:
https://github.com/michael-o/activedirectory-dns-locator/blob/9dff8dfb3fce8890a8166be6de89b9c05ef77108/pom.xml#L101-L114
Here is my proposal: Before we go over on how to integrate, we should first
agree on a minimal diff because I see stuff we can be reduced even further
and/or precediing work to make life for you easier. Please open a draft PR to
discuss this first. I hope to get this into the upccoming release. Meanwhile I
will prepare a new Velocity Parent POM release.
> VelocityViewServlet extending from jakarta.servlet instead of javax.servlet
> ---------------------------------------------------------------------------
>
> Key: VELTOOLS-202
> URL: https://issues.apache.org/jira/browse/VELTOOLS-202
> Project: Velocity Tools
> Issue Type: New Feature
> Components: VelocityView
> Reporter: David Ruiz de Azua
> Priority: Trivial
>
> To whom may concern,
> Currently VelocityViewServlet extends from javax rather than jakarta.
> Due the cutover from Java to Jakarta, *is there any plan to make Apache
> Velocity compatible with Servlet 5.0?*
> Not sure if there are any plans to make the transition to Jakarta namespace
> and if there is any ETA for it.
> [https://jakarta.ee/specifications/servlet/5.0/apidocs/jakarta/servlet/http/httpservlet]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
