com/bitstorm/Wicket-tutorial-examples.git If you aren’t used to Git, you can simply download the whole source as a zip archive: The repository contains a multi-module Maven project. Every subproject is contained have their pros and cons, there are good reasons to prefer Wicket over them: • Wicket is 100% open source: Wicket is a top Apache project and it doesn’t depend on any private company. You don’t have to Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through

com/bitstorm/Wicket-tutorial-examples.git If you aren’t used to Git, you can simply download the whole source as a zip archive: The repository contains a multi-module Maven project. Every subproject is contained have their pros and cons, there are good reasons to prefer Wicket over them: • Wicket is 100% open source: Wicket is a top Apache project and it doesn’t depend on any private company. You don’t have to Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through

com/bitstorm/Wicket-tutorial-examples.git If you aren’t used to Git, you can simply download the whole source as a zip archive: The repository contains a multi-module Maven project. Every subproject is contained have their pros and cons, there are good reasons to prefer Wicket over them: • Wicket is 100% open source: Wicket is a top Apache project and it doesn’t depend on any private company. You don’t have to Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through

com/bitstorm/Wicket-tutorial-examples.git If you aren’t used to Git, you can simply download the whole source as a zip archive: The repository contains a multi-module Maven project. Every subproject is contained have their pros and cons, there are good reasons to prefer Wicket over them: • Wicket is 100% open source: Wicket is a top Apache project and it doesn’t depend on any private company. You don’t have to Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through

● We had a quick “journey” through the life of Wicket. ● As for any other Open Source project, the health of its community is fundamental. ● We have seen some of the most appealing features, still