Skip to content

Conversation

pepness
Copy link
Member

@pepness pepness commented Aug 28, 2025

  • Tomcat 7-11 runs on Java SE 26
  • TomEE 10 runs on Java SE 17 and later
  • TomEE 9-8 runs up to Java SE 23
  • Add enum for Java SE 26 on GlassFish tooling (currently not supported by GlassFish)

NetBeans Testing:

  • Verify successful execution of libraries and licenses Ant test
  • Verify successful execution of Verify Sigtests
  • Verify successful execution of unit tests for modules glassfish.common, glassfish.javaee, glassfish.tooling, glassfish.eecommon, and tomcat5
  • Started NetBeans and ensure the log didn't have any ERROR or new WARNINGS
  • Successfully register Tomcat 7-11 & TomEE 8-10.
    • Create a Jakarta EE 11 maven web app and verify that it works
    • Create a Jakarta EE 11 ant web app and verify that it works.

- Tomcat 7-11 runs on Java SE 26
- TomEE 10 runs on Java SE 17 and later
- TomEE 9-8 runs up to Java SE 23
- Add enum for Java SE 26 on GlassFish tooling
@pepness pepness added this to the NB28 milestone Aug 28, 2025
@pepness pepness self-assigned this Aug 28, 2025
@pepness pepness added Java EE/Jakarta EE [ci] enable enterprise job enterprise [ci] enable enterprise job labels Aug 28, 2025
Copy link
Contributor

@matthiasblaesing matthiasblaesing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only eyeballed this, but looks sane. I'm a bit surprised, that Tomcat does not use the security manager, but great, that it seems JakartaEE slowly gets into stable waters not breaking on each java update.

@pepness pepness merged commit f0d9562 into apache:master Aug 31, 2025
59 of 60 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enterprise [ci] enable enterprise job Java EE/Jakarta EE [ci] enable enterprise job
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants