[CONF] Apache Wicket: Wicket SVN (page edited)

[confluence]

Page Edited : WICKET : Wicket SVN Wicket SVN has been edited by Nick Heudecker (Apr 21, 2007). Change summary: Trying to update the page to reflect the wicket 2.0 cancellation/1.3 moving to trunk stuff. (View changes) Content: Table of contents Structure trunk branches tags releases Committers Based on Martijn's New subversion repository structure email to the lists - Gwyn 08:28, 28 Aug 2006 (BST) As you know, we are working in a forked mode: wicket 1.3 is under active development, and we also provide support for wicket 1.2 (1.2.5 has just been released). Development on the Wicket 2.0 branch has been terminated and 1.3 is now the trunk. Wicket 1.3 We've created the wicket-1.2.x branch. This means that from now on Wicket 1.2 will be in maintenance mode only. Trunk is now reserved for 1.3 development. This page tries to clarify how to use our subversion repository. Structure If you look at the repository you will see the following root structure: /trunk/ - (/trunk/ via ViewVC) [ /branches/|http://svn.apache.org/repos/asf/incubator/wicket/branches/] (/branches/ via ViewVC) /tags/ - (/tags/ via ViewVC) /releases/ - (/releases/ via ViewVC) trunk trunk is used for the development of the most recent major release of wicket. In this case, that is Wicket 1.3. branches branches is used for the development of older major versions, when these are in active development. It is also used for bug fixing older releases. Currently you'll find the following directories there: branches/wicket-1.0.x <- bug fixes for 1.0 (now unsupported) branches/wicket-1.1.x <- bug fixes for 1.1 (now unsupported) branches/wicket-1.2.x <- bug fixes for 1.2 (maintenance mode) branches/wicket-1.x <- development for newest minor version of wicket 1 (currently wicket 1.3). So if you are asked to check out wicket 1.3, then you'll have to check out branches/wicket-1.x. If you want the latest sources for Wicket 1.2, then you'll have to check out branches/wicket-1.2.x tags The tags directory is used for creating patches against a particular release. For instance, if you have a patch that you want to submit for wicket 1.2.2, then you'll have to create the patch against: tags/wicket-1.2.2 releases The releases directory contains all project files that were used for building a release, after creating the release. This means that the maven pom.xml files are changed to reflect the specific versions. So if you want to rebuild a particular release yourself, say 1.2.2, you can checkout releases/wicket-1.2.2. This will give you the exact sources that went into the release, including correctly dependent project files. Do not use these releases to create patches, use tags for that! If you have questions, please don't hesitate to ask on ##wicket or the mailing lists. Committers Note, committers should use http*s*://svn.apache.org/repos/asf/incubator/wicket/.. URLs which will trigger authentication for changes!

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences