Skip to content

Build against Wicket 12.0.0-SNAPSHOT - #1683

Open
dashorst wants to merge 1 commit into
masterfrom
move-to-wicket-12
Open

dashorst wants to merge 1 commit into
masterfrom
move-to-wicket-12

Conversation

@dashorst

Copy link
Copy Markdown
Member

The default branch moves to 12.0.0-SNAPSHOT and builds against Wicket 12.0.0-SNAPSHOT. Wicket 11 work continues on the new wicket-11.x branch (created at 16e52a6, still 11.0.0-SNAPSHOT on Wicket 11.0.0 so wicketstuff 11.0.0 can be released from it).

Changes:

  • all module poms: 11.0.0-SNAPSHOT → 12.0.0-SNAPSHOT (mvn versions:set)
  • wicket.version: 11.0.0 → 12.0.0-SNAPSHOT
  • .github/dependabot.yml: add a wicket-11.x maven job that ignores semver-major updates, same as wicket-10.x

Wicket 12.0.0-SNAPSHOT still targets Java 21, so the compiler settings stay.

🤖 Generated with Claude Code

Development moves to Wicket 12; Wicket 11 maintenance continues on the
new wicket-11.x branch. Add a dependabot block for wicket-11.x that
ignores semver-major updates, like the one for wicket-10.x.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dashorst
dashorst marked this pull request as ready for review November 11, 2026 23:20
Comment thread pom.xml Resolved
@dashorst

Copy link
Copy Markdown
Member Author

There's no org.eclipse.jetty.ee12 on Central yet (no Jetty 13 either), and Wicket 12.0.0-SNAPSHOT itself still uses jetty-ee11-webapp 12.1.14 with Servlet 6.1. I'd keep ee11 for now and switch when Jetty ships EE 12 and Wicket moves to it. Or do you have a repository where the ee12 artifacts live?

This branch was successfully deployed

1 active deployment
CI_DEPLOY — 7ae64e18 Deployed Nov 11, 2026 by dashorst via Java 21 Test #1981
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.

2 participants