dashorst opened a new pull request, #1930:
URL: https://github.com/apache/wicket/pull/1930

   Fixes #1926. Backport of #1895 (Richard's commit 8384e37ed3, cherry-picked 
with `-x`, author kept) to wicket-10.x: adds `org.apache.wicket:wicket-bom`, 
whose published POM is generated by bom-builder3 1.3.4 from the reactor and 
manages only the published Wicket modules, without a parent or scopes.
   
   Adapted for 10.x in `wicket-bom/pom.xml`: parent version 10.13.0-SNAPSHOT, 
experimental groupId `org.apache.wicket.experimental.wicket10`, and no 
exclusions for wicket-benchmarks and wicket-coverage, which the 10.x reactor 
doesn't have. The exclusion list matches the modules that skip deploy on 10.x: 
wicket-core-tests, wicket-cdi-tests, wicket-common-tests, wicket-js-tests and 
wicket-user-guide. The only conflict was in the plugin version properties in 
the root pom; 10.x's build-helper-maven-plugin 3.8.0 is kept.
   
   The generated BOM lists 22 artifacts at 10.13.0-SNAPSHOT: wicket (pom), 
wicket-auth-roles, wicket-bean-validation, wicket-cdi, wicket-core, 
wicket-devutils, wicket-extensions, wicket-extensions-tester, wicket-guice, 
wicket-ioc, wicket-jmx, wicket-migration, wicket-native-websocket-core, 
wicket-native-websocket-javax, wicket-native-websocket-tester, 
wicket-objectsizeof-agent, wicket-request, wicket-spring, wicket-tester, 
wicket-util, wicket-velocity, and 
`org.apache.wicket.experimental.wicket10:wicket-metrics`.
   
   Tested with `mvn clean verify -Pjs-test` (Maven 3.9.16, Java 21): all 
modules pass; japicmp skips wicket-bom because its packaging is pom. A consumer 
project that imports the BOM with `<scope>import</scope>` resolves 
`wicket-core` without a version.
   
   Documentation in the migration guide is tracked in #1925.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to