papegaaij opened a new pull request, #1730: URL: https://github.com/apache/wicket/pull/1730
Fixes #1724 Since the quickstart archetype is tested during the build, its pom runs `maven-invoker-plugin:install` to give the generated project the Wicket modules it needs. Without a `localRepositoryPath` that goal installs into the user's own local repository, so a plain `mvn verify` left 17 Wicket files in `~/.m2`, marked as locally installed and therefore never re-downloaded. After verifying a release candidate those were jars with the final release version built from the RC, which would silently shadow a later RC reusing the version number. `invoker:install` and `archetype:integration-test` now share a local repository at `target/it-repo`, set through the `archetype.test.localRepositoryPath` property. The generated project resolves Wicket from there and fetches everything else through the user's normal settings, mirrors included. The cost: a clean build downloads the integration test's third-party dependencies (about 56 MB, mostly Maven plugins) into `target/it-repo` again. Reading them from `~/.m2` instead would need a custom settings file for the integration test, which replaces the user's settings and so drops their mirrors and proxies. Nothing changes for applications. Verified with `mvn clean verify -Pjs-test`: green, and nothing new under `~/.m2/repository/org/apache/wicket` afterwards. This is on master only for now; the `wicket-10.x` backport follows separately. 🤖 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]
