Skip to content

Update starter to include Liberty for Jakarta EE 11#382

Merged
m-reza-rahman merged 2 commits into
eclipse-ee4j:masterfrom
jhanders34:jha_branch1
Jun 13, 2026
Merged

Update starter to include Liberty for Jakarta EE 11#382
m-reza-rahman merged 2 commits into
eclipse-ee4j:masterfrom
jhanders34:jha_branch1

Conversation

@eclipse-starter-bot

Copy link
Copy Markdown

Can one of the admins verify this patch?

@m-reza-rahman m-reza-rahman marked this pull request as draft May 21, 2026 21:41
@m-reza-rahman

Copy link
Copy Markdown
Contributor

Once there is actual certification, please take this out of draft mode. I'll review it at that point. Thanks!

@jhanders34 jhanders34 marked this pull request as ready for review May 26, 2026 03:03
@jhanders34

Copy link
Copy Markdown
Member Author

All CCRs were marked accepted

@jhanders34

Copy link
Copy Markdown
Member Author

FYI @m-reza-rahman

@m-reza-rahman

Copy link
Copy Markdown
Contributor

I'll take a look ASAP. Currently trying to stabilize a long pending release. Should get to it by the end of the weekend hopefully.

@m-reza-rahman m-reza-rahman self-assigned this May 28, 2026
Comment thread ui/src/main/webapp/index.xhtml Outdated
value="Java SE 11 requires Jakarta EE below 11."/>
<h:outputText
styleClass="footnote"
value="Java SE 8 requires Jakarta EE below 10."/>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Minor comment... the "spirit" of the rewording above is to say " EE 10 requires Java SE 11..." rather than "..above 8". By the same token you might say "SE 8 requires EE 9.1 or below" instead of "..below 10".

Comment thread ui/src/main/webapp/index.xhtml Outdated
value="Jakarta EE 11 requires Java SE 17 or later."/>
<h:outputText
styleClass="footnote"
value="Jakarta EE 10 requires Java SE 11 or later."/>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Noting the others combine the text into one <h:outputText> with a two-sentence value, but I think this is maybe more readable.

@m-reza-rahman m-reza-rahman May 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, please fix. The same for the next change.

@scottkurz scottkurz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think you need to change this line..it fails if I actually run mvn archetype:generate and select Open Liberty with EE 11.

archetype-post-generate.groovy: throw new RuntimeException("Failed, only Payara currently supports Jakarta EE 11 in a stable release")

#else
<feature>webProfile-11.0</feature>
#end
#else

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please remove this for now. We'll add it when EE 12 is a bit more real.

<feature>webProfile-10.0</feature>
#end
#else
#elseif (${jakartaVersion} == '11')

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please remove this. EE 11 can be the fallback case.

runtimes.get("glassfish").setDisabled(false);
}

if (jakartaVersion == 11) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This else-if block can now be removed altogether.

@m-reza-rahman

Copy link
Copy Markdown
Contributor

I think you need to change this line..it fails if I actually run mvn archetype:generate and select Open Liberty with EE 11.

archetype-post-generate.groovy: throw new RuntimeException("Failed, only Payara currently supports Jakarta EE 11 in a stable release")

Yes, this change is entirely missing. The right thing to do at this point is remove the EE 11 catch- all validation and move it to the runtime specific sections. We will need to soon enable GlassFish for EE 11 too, so this change is timely. The correcpionding nightly tests need to be updated as well.

@m-reza-rahman m-reza-rahman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please address comments. After that, I'll review again.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Enables Open Liberty as a selectable/runtime-tested target for Jakarta EE 11 in the starter UI and archetype outputs, aligning UI guidance and CI coverage with the Jakarta EE 11 Java SE baseline.

Changes:

  • Updated UI footnotes to explicitly state Java SE requirements for Jakarta EE 10 vs 11, and clarified Java SE 8 constraints.
  • Allowed Open Liberty to be selectable for Jakarta EE 11 in the UI runtime enablement logic.
  • Extended Open Liberty archetype config and nightly workflow coverage to include Jakarta EE 11 (Java 17 and 21; full/web/core profiles) with Docker builds.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
ui/src/main/webapp/index.xhtml Updates UI footnotes to reflect Jakarta EE 10/11 Java SE requirements and Java SE 8 constraints.
ui/src/main/java/org/eclipse/starter/ui/Project.java Adjusts runtime enablement so Open Liberty is no longer disabled for Jakarta EE 11.
archetype/src/main/resources/archetype-resources/src/main/liberty/config/server.xml Refines Liberty feature selection logic for Jakarta EE 11 (and adds a fallback for 12).
.github/workflows/nightly.yml Adds nightly archetype + Docker build validation for Jakarta EE 11 on Open Liberty (Java 17 and 21; multiple profiles).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jhanders34

Copy link
Copy Markdown
Member Author

@m-reza-rahman and @scottkurz I have addressed your review comments I believe.

@m-reza-rahman

Copy link
Copy Markdown
Contributor

OK, will look ASAP, thanks.

@scottkurz scottkurz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Tested the UI and archetype:generate a bit and my comments seem addressed.

@m-reza-rahman m-reza-rahman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. I’ll take it from here.

@m-reza-rahman m-reza-rahman merged commit 60a5503 into eclipse-ee4j:master Jun 13, 2026
3 checks passed
@jhanders34

Copy link
Copy Markdown
Member Author

@m-reza-rahman I see that it is merged, but it appears that start.jakarta.ee hasn't been updated to have the new code deployed. When will that happen?

@m-reza-rahman

Copy link
Copy Markdown
Contributor

We also need to update for GlassFish. Probably in a few weeks?

@m-reza-rahman

Copy link
Copy Markdown
Contributor

Also, @jhanders34 - it looks like the merge has broken the nightly build: https://github.com/eclipse-ee4j/starter/actions/runs/27994183766/job/82852778584. Can you kindly take a look? Otherwise, this is one more thing I need to do.

@jhanders34

Copy link
Copy Markdown
Member Author

Also, @jhanders34 - it looks like the merge has broken the nightly build: https://github.com/eclipse-ee4j/starter/actions/runs/27994183766/job/82852778584. Can you kindly take a look? Otherwise, this is one more thing I need to do.

@m-reza-rahman I created PR #383 which should resolve this issue.

@m-reza-rahman

Copy link
Copy Markdown
Contributor

Merged. Hopefully that was it.

@jhanders34

Copy link
Copy Markdown
Member Author

Merged. Hopefully that was it.

Last night's nightly build was good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants