-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Mark,
On 1/14/20 12:15 PM, Mark Thomas wrote: > On 14/01/2020 17:07, Christopher Schultz wrote: >> Mark, >> >> On 1/14/20 11:58 AM, Mark Thomas wrote: >>> On 14/01/2020 16:54, ma...@apache.org wrote: >>>> This is an automated email from the ASF dual-hosted git >>>> repository. >>>> >>>> markt pushed a commit to branch master in repository >>>> https://gitbox.apache.org/repos/asf/tomcat.git >>>> >>>> >>>> The following commit(s) were added to refs/heads/master by >>>> this push: new 280bb15 Add spec updates to changelog 280bb15 >>>> is described below >>>> >>>> commit 280bb15bdb4dbb428151866eeac606e638896cb4 Author: Mark >>>> Thomas <ma...@apache.org> AuthorDate: Tue Jan 14 16:54:13 >>>> 2020 +0000 >>>> >>>> Add spec updates to changelog >> >>> My plan for the 10.0.0.0-M1 changelog was to only include >>> entries that are not back-ported to 9.0.x. 10.0.0.0-M1 will be >>> released alongside a 9.0.x release and the announcement will >>> state it is based on that 9.0.x version. >> >>> For 10.0.0.0-M2 onwards, we would include all changes, >>> included those that were back-ported. >> >>> Thoughts? >> >> That may be confusing, since AIUI in the past, the changelog for >> X.0.0 has always been relative to (X-1).current when the branch >> was made (right)? > > Only because we created the branch immediately after the tag. That > didn't happen in this case. > >> Perhaps we could just put a note at the top indicating your >> proposed policy if you want to go that way. > > We could add something in the General section. > >> Off-topic: if you have indeed written a >> mass-search-and-replace-tool for switching from javax.servlet -> >> jakarta.servlet, is that something you are going to publish? > > I just used the built-in Eclipse rename and find/replace to update > Tomcat. > > When I updated the Jakarta Server Pages project for the updated EL > and Servlet APIs, a simple find and replace was all that was > required. Oh, I know that. But, for example, I'm not sure what the list of old/new APIs are. Clearly "javax.servlet" -> "jakarta.servlet", but what other APIs need to be converted also? Even a simple sed script would be useful to someone who wants to take an application that it running successfully on Tomcat 9 and try to run it on Tomcat 10. > The tool I used to convert JSTL from javax to jakarta which I did > entirely without access to the source (although we have it sat > there in svn) is available at: > https://github.com/apache/tomcat-jakartaee-migration Cool, I'll have a look. - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl4eBHUACgkQHPApP6U8 pFg4JxAArV3Ce6Lak52GlEZ2j8wI3frDXvTqB2F8iciUfAntexyGHUtr5rq90/Me AGqxV93kDLjhwXKMQAj+iAbG+LullmkUBgFzfciQATSC8a4vekrtCnAqykFa7wPM gYlYXuX6hybXl+vuU0rQMuoMTnMEmEbGch8yhQoezW0r4bvGA6C+cwEQKjiPPZf6 DWP3YhiPgYD6j41ic0+nos+Rvkq4CsX++74rNQIXJmaIJ3b3wM4gVChdBQqlUy35 WXwlZsk3yElD/Le63eFDWNJ36934BlSPb2/COGuqsUrxLHGj4EnXTIPK6AwJEoeE baIgp3mIddqNS7IwCRNwjp/1hfdvxnIpgxfnBvuJ7zf1Lcq0OskQesLpccinI9ja 4tE8wnWfcvl8Vp6Mg340Vl/d+LJWU0cuKkDa5QHKtmluHmRUB3FwUqXk4ldow40c yNocpUpRcxm7WyMe0188KxkTigfwnFB6n1KX12XHXkDyvmLqJYVS2YUmLYlCpb/q 97O4onVm53AWufHInKceZKGvkX0WMk/UJIUo2MoxdAefWcxd60pSZFKyhlK9rbHm OWRXu7dtN2tlT2GCMTu22nj73GhJyCXuQeRKQpOH0S1tDEZ5EO8INc6p+9izSVHE t52QkjogoI4caED/jyzcMuJ44x146509jmlgABSrb9z4BOYIGjg= =yutY -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
