Skip to content

Fixes issue #1658: quickstart is tested during build - #1664

Open
solomax wants to merge 3 commits into
wicket-10.xfrom
quickstart-fix2
Open

solomax wants to merge 3 commits into
wicket-10.xfrom
quickstart-fix2

Conversation

@solomax

@solomax solomax commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@solomax solomax self-assigned this Oct 13, 2026
@solomax
solomax requested a review from dashorst October 13, 2026 04:05
The archetype integration test ran clean verify on the generated project
with whatever Wicket artifacts the local repository or the Apache
snapshot repository held. CI runs verify without install, and the
archetype module did not depend on the modules the generated project
uses, so the reactor could even build it before them. A change to
wicket-core or wicket-native-websocket-javax was tested against the
previous nightly snapshot, and right after a version bump the generated
project could not resolve Wicket at all until a snapshot of the new
version was published.

The archetype module now declares the generated project's Wicket
modules as test dependencies, which orders it after them in the reactor,
and maven-invoker-plugin:install copies them, their reactor dependencies
and their parent poms into the local repository before the integration
test runs. A plain mvn verify therefore writes these snapshots to the
local repository, as mvn install would have. The installation and the
integration test both follow -DskipTests, so a build that skips tests no
longer generates and builds a project; -Darchetype.test.skip still skips
the integration test alone.

Start.java loses what was left over from Jetty 11: the unused session
store imports, the commented-out session cache line and the obsolete
JSR-356 instructions. The JSESSIONID hint uses the Jetty 12 session
handler API, and the HTTP idle timeout is the literal it was before.

GitHub issue #1658

Generated-by: Claude Code (Claude Opus 5.5)
The previous commit turned the idle timeout back into 1000 * 60 * 60,
undoing the Duration the original port introduced. Duration.ofHours(1)
states the intent more plainly; toMillis() is passed as is, because
setIdleTimeout takes a long and needs no cast to int. The timeout stays
one hour, and the HTTPS connector keeps its own value.

GitHub issue #1658

Generated-by: Claude Code (Claude Opus 5.5)
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.

The quickstart archetype's Start.java does not compile against Jetty 12

2 participants