https://bugzilla.redhat.com/show_bug.cgi?id=1868992 --- Comment #4 from Mat Booth <mat.booth@xxxxxxxxxx> --- (In reply to Fabio Valentini from comment #3) > Hm. Well, we could switch to shipping an older version of jsp-api for now > (one that doesn't have the package name transition yet). According to an > upstream developer, those latest "stable" releases aren't even meant for > public consumption yet :( > That might be the easiest thing to do. I suspect there won't be many differences except the package name refactoring between the last 2.x.x release and 3.0.0. > https://github.com/eclipse-ee4j/jaf/issues/49 > > No idea why they're tagged as "x.0.0" releases in GitHub if they're not > ready yet :D I suppose they expect people to check maven central, the canonical distribution method for java, where the github-tagged release is not yet available: https://search.maven.org/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-api -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
