You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document the wicket-bom and how to import it #1925
Pull request #1895 (GitHub issue #1894) adds org.apache.wicket:wicket-bom, a BOM that manages the versions of the published Wicket modules and of no third-party libraries. Nothing in the documentation mentions it yet; the only pointer to version management is the README's reference to the wicket-parent pom.
The documentation should cover:
importing the BOM in <dependencyManagement> with <type>pom</type> and <scope>import</scope>, and then declaring Wicket modules without a version
why to import wicket-bom rather than wicket-parent: the parent carries the whole build's dependency management (third-party versions and scopes), which overrides other BOMs depending on import order and makes Maven 4 warn about conflicting management
which artifacts the BOM manages, including wicket-metrics under the experimental groupId
a Gradle example (implementation platform("org.apache.wicket:wicket-bom:<version>"))
Places to update: the user guide (the chapter on setting up a project / Maven), the README, the quickstart archetype's generated pom if it should use the BOM, and migration-to-12.md in the repository root (plus the 10.x/11.x migration guides if the BOM is backported).
Activity