Hi all, I am very sorry, I made a fatal mistake when fixing tomcat-jakartaee-migration #29 issue, which led to #34 issue.
I have re-fixed this issue with this solution: https://github.com/aooohan/tomcat-jakartaee-migration/blob/e07f9cb21b36fe44ef31cc97e39e2c1657a94424/src/main/java/org/apache/tomcat/jakartaee/Migration.java#L226-L239 <https://github.com/aooohan/tomcat-jakartaee-migration/blob/e07f9cb21b36fe44ef31cc97e39e2c1657a94424/src/main/java/org/apache/tomcat/jakartaee/Migration.java#L226-L239> （I 'll continue optimising code tomorrow, it's late and I'm sleepy.） I will retest it tomorrow to make sure the problem is really fixed. But I don't know if this will affect the release tasks , like 10.1.x or other version. How will we handle this situation, possibly by continuing to release tomcat-jakartaee-migration 1.0.4? Best Regard Han
