On 22/07/2020 15:53, Mark Thomas wrote: > Hi all, > > We currently have implementations for all of the Jakarta APIs that ship with > Tomcat and partial implementations for 5 additional Jakarta APIs that are > compile time only dependencies. > > I was checking those partial implementations earlier today when I noticed the > Jakarta Mail API needed updating to use generics. I started on that but > paused when it looked like a number of new (dummy) classes would be required. > > Considering alternative options, I wondered about depending on the Jakarta > API JARs directly. This would be a return to the 5.5.x era approach without > hopefully, the issue that JARs could be difficult to obtain. > > I have this implemented locally. It removes about 1000 lines of .java files > (although just under 10% of them are actual code) and adds about 100 lines of > build file config and anither 50 of IDE configuration. > > With the Jakarta JARs being readily available in Maven Central I think the > primary issue that led to the current approach is no longer a concern. > > Thoughts on switching to using the JARs directly? I can provide a PR if that > is helpful.
For clarity, I'm only proposing to do this for Tomcat 10 where at least one of these APIs has changes other than just a package rename. I don't see the benefit in doing this for Tomact 9 and earlier. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
