Repository navigation
Conversation
wicket-util and wicket-request were not managed, so wicket-bootstrap-core
7.0.16 put Wicket 10.12.0 versions of them on the classpath of
wicketstuff-openlayers3-bootstrap, next to wicket-core 11.0.0. This
shipped in 11.0.0.
Manage wicket-util, wicket-request, wicket-native-websocket-core,
wicket-cdi and wicket-bean-validation at ${wicket.version}, and add a
bannedDependencies rule that fails the build when any org.apache.wicket
artifact on a classpath has another version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
solomax
approved these changes
Nov 14, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wicketstuff 11.0.0 shipped
wicketstuff-openlayers3-bootstrapwithwicket-requestandwicket-util10.12.0 on its classpath next towicket-core11.0.0. The root pom managedwicket-coreandwicket-extensions, but notwicket-utilandwicket-request, so the versions declared bywicket-bootstrap-core7.0.16 (built on Wicket 10.12.0) won. This is a fix for 11.0.1.Changes, all in the root
pom.xml:wicket-util,wicket-request,wicket-native-websocket-core,wicket-cdiandwicket-bean-validationat${wicket.version}bannedDependenciesrule to theenforce-versionsexecution: onlyorg.apache.wicket:*:${wicket.version}is allowed on any module's classpathVerification:
wicketstuff-openlayers3-bootstrap:wicket-bootstrap-core:7.0.16→wicket-request:10.12.0/wicket-util:10.12.0bannedmvn -DperformRelease=true -Pdo-publish clean verify(javadoc and sources on, GPG skipped) succeeds for all 206 modulesmvn dependency:tree -Dverbose -Dincludes=org.apache.wicketover the whole reactor: all 1494 Wicket references resolve to 11.0.0Moving
wicket-bootstrap-corefrom 7.x (the Wicket 10 line) to 8.x is a separate change. Same fix for master andwicket-10.x: #1687 and #1688.🤖 Generated with Claude Code