Question 1

How do I add a Wicket Stuff module to my Maven project?

Accepted Answer

Add the dependency with a version matching your Wicket version, e.g., for Wicket 1.4.16, use a module version like 1.4.16.1. Check Maven Central or the GitHub repo for specific group and artifact IDs.

Question 2

What's the difference between Wicket Stuff Core and official Apache Wicket extensions?

Accepted Answer

Wicket Stuff Core is community-driven with a broad acceptance policy, offering diverse but potentially less standardized modules. Official extensions are more curated and maintained by the Apache Wicket team for reliability.

Question 3

Are all modules in Wicket Stuff production-ready?

Accepted Answer

Not necessarily. Due to the broad acceptance criteria, some modules might be experimental or poorly maintained. Always review individual module documentation and community feedback before deploying in production.

Question 4

How often does Wicket Stuff release new versions?

Accepted Answer

Releases are synchronized with Apache Wicket versions. When a new Wicket version is out, Wicket Stuff modules are updated, but point releases for bug fixes might occur independently based on community contributions.

Question 5

Can I use Wicket Stuff with Gradle or other build tools?

Accepted Answer

Yes, since artifacts are published to Maven Central, you can use them with any build tool that supports Maven repositories, such as Gradle, by adding the appropriate dependency coordinates.

Question 6

What if I need a module that isn't updated for the latest Wicket version?

Accepted Answer

You may need to wait for the next synchronized release or contribute an update yourself, as maintenance relies on volunteer efforts. Check the GitHub repo for open issues or fork the module to make changes.

Annotation

What is Annotation?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions