Ask a question
The documentation answers most questions; its search finds a class, a task or an error message. When it does not, ask the people who build with Wicket every day:
- The users list, users@wicket.apache.org, is where most questions get answered, by users and committers alike. Subscribe first by mailing users-subscribe@wicket.apache.org; only subscribers can post. Twenty years of answers are in its archive.
- Slack: the #wicket channel on the ASF Slack is for a quicker conversation, though time zones can make it quiet. Committers sign in with their apache.org account; anyone else joins as a guest by invitation, so ask for one on the users list. The ASF’s Slack guidelines explain how guest access works.
-
Stack Overflow has years of answered questions under the
wickettag.
Include your Wicket and Java versions and what you tried. A question with a few lines of code and the full stack trace gets a better answer, sooner.
Commercial support
Several companies offer training, consulting and development for Wicket applications. The wiki keeps a list of service providers. The Wicket project does not endorse or rank them.
Report a bug
Report bugs in the issue tracker on GitHub. A report the committers can reproduce gets fixed first:
- Search first. Look for your problem in the open and closed issues, and in the JIRA archive for issues from before 2026.
- Try the latest release of your line. Your bug may already be fixed. If your line is out of service, it gets no more fixes; reproduce it on a line in service.
- Reproduce it in a quickstart. Generate a small project with the quick start and add only what shows the problem. Often this alone reveals the cause; otherwise it is the fastest way for a committer to see it.
- Open the issue with the Wicket version, the Java version and servlet container, the steps to reproduce, what you expected, the full stack trace, and a link to your quickstart, for example as a GitHub repository.
A failing test with WicketTester, or a pull request with the fix, is better still: see Contribute.
Report a vulnerability
Never report a security problem in the issue tracker or on a mailing list: both are public. Send it to private@wicket.apache.org, the private list of the Wicket PMC. Describe the problem, the versions it affects, and how to reproduce it.
The PMC follows the ASF’s process for vulnerabilities: it confirms the problem, fixes it in the lines in service, and publishes an advisory with a CVE on the blog and the announce list once a fixed release is out. Only security reports belong on this list; for anything else, use the users list or the issue tracker.
Mailing lists
The project’s lists, with their archives on lists.apache.org. Subscribe to a list by sending an empty mail to its subscribe address; only subscribers can post.
| List | For | Subscribe | Archive |
|---|---|---|---|
| users@ | Questions and answers about using Wicket. | users-subscribe@ | Archive |
| dev@ | Wicket's development: plans, changes, releases and votes. | dev-subscribe@ | Archive |
| announce@ | Releases and security advisories only; only the PMC posts. | announce-subscribe@ | Archive |
| commits@ | Every commit and issue update, sent automatically. Read only. | commits-subscribe@ | Archive |
Releases and advisories also appear on the blog and in its Atom feed.
Contribute
Wicket is built by the people who use it, and help is welcome at every level: answering a question, improving a page of the documentation, fixing a bug. Contribute shows where to start.
Built with Wicket
Many applications run on Wicket without saying so. Show yours on Built with Wicket.
The project
Apache Wicket is a project of the Apache Software Foundation, run by its Project Management Committee and developed in the open by its committers and contributors. Everyone taking part follows the ASF’s code of conduct.