On Wed, Sep 14, 2022 at 6:43 PM Han Li <li...@apache.org> wrote: > > Hi all, > > I am very sorry, I made a fatal mistake when fixing > tomcat-jakartaee-migration #29 issue, which led to #34 issue.
Well, when you do things, you're more likely to break things. So no need to apologize. > 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? With a regression, a 1.0.4 is needed, then start over the 10.1 and 10.0 release process. Good thing my internet access is "dead" (I hope it will be fixed tomorrow), I haven't started 9.0 yet. Rémy > > Best Regard > > Han --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
