You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by ad...@apache.org on 2014/04/26 22:03:30 UTC
svn commit: r1590290 [7/10] - in /wicket/common/site/trunk: ./ _posts/
_site/ _site/2009/07/30/ _site/2009/08/21/ _site/2009/10/12/
_site/2009/10/24/ _site/2009/12/13/ _site/2009/12/21/ _site/2010/02/01/
_site/2010/03/05/ _site/2010/05/03/ _site/2010/0...
Modified: wicket/common/site/trunk/_site/contribute/build.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/build.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/build.html (original)
+++ wicket/common/site/trunk/_site/contribute/build.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -188,9 +188,9 @@
<li>Using your own built artifacts</li>
</ol>
-<p>For more information on the project structure, please read the âBetter Builds With Mavenâ book which has a detailed description on how to structure a maintainable, enterprise ready build. The book is available for free from the Mergere website.</p>
+<p>For more information on the project structure, please read the ‘Better Builds With Maven’ book which has a detailed description on how to structure a maintainable, enterprise ready build. The book is available for free from the Mergere website.</p>
-<h2 id="getting_your_wicket_version">Getting your Wicket version</h2>
+<h2 id='getting_your_wicket_version'>Getting your Wicket version</h2>
<p>Clone the master branch from Apache Git Wicket repository</p>
<div class='highlight'><pre><code class='console'><span class='gp'>$</span> git clone http://git-wip-us.apache.org/repos/asf/wicket.git
@@ -213,15 +213,15 @@
</code></pre></div>
<p>In this document we focus at the maven project descriptor located in the top level directory, which enforces default settings for all Wicket projects such as plug-in settings, versioning of the Wicket projects, managing the various dependencies and more.</p>
-<p>The artifacts in this project are there only for having a consistent build. This top-level project doesnât have sources for itself.</p>
+<p>The artifacts in this project are there only for having a consistent build. This top-level project doesn’t have sources for itself.</p>
-<h2 id="building_wicket">Building Wicket</h2>
+<h2 id='building_wicket'>Building Wicket</h2>
<p>The current development version of Wicket requires at least jdk 6.</p>
<p>If you want to ensure that your Wicket version is built using JDK-6 and fully compatible with that Java version, you will need to build it with a Java 6 compiler and runtime library.</p>
-<p>If you havenât done so already change into the Wicket root directory:</p>
+<p>If you haven’t done so already change into the Wicket root directory:</p>
<div class='highlight'><pre><code class='console'><span class='go'>cd wicket</span>
</code></pre></div>
<p>Now building all of Wicket is as simple as issuing the following command:</p>
@@ -240,14 +240,14 @@
</table>
<p>You can just run the install target, as Maven will build the previous stages automatically.</p>
-<h3 id="coping_with_test_failures">Coping with test failures</h3>
+<h3 id='coping_with_test_failures'>Coping with test failures</h3>
<p>As this is our main development you might/will encounter failing unit tests. These can be skipped using:</p>
<div class='highlight'><pre><code class='console'><span class='go'>mvn -Dmaven.test.skip=true install</span>
</code></pre></div>
<p>Of course, all bets are off then and your mileage may vary if you use such a built jar.</p>
-<h3 id="using_your_own_built_artifacts">Using your own built artifacts</h3>
+<h3 id='using_your_own_built_artifacts'>Using your own built artifacts</h3>
<p>Now you have built your own fresh Wicket jar you must be anxious to use it. This is now as simple as adding a snapshot dependency on the specific Wicket version. So in your pom.xml you can use:</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
@@ -257,7 +257,7 @@
<span class='nt'><scope></span>compile<span class='nt'></scope></span>
<span class='nt'></dependency></span>
</code></pre></div>
-<p>Read <a href="../learn/ides.html">IDE support</a> to learn how to continue from here with an IDE.</p>
+<p>Read <a href='../learn/ides.html'>IDE support</a> to learn how to continue from here with an IDE.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/contribute/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/index.html (original)
+++ wicket/common/site/trunk/_site/contribute/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/contribute/patch.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/patch.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/patch.html (original)
+++ wicket/common/site/trunk/_site/contribute/patch.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,24 +174,24 @@
<div id="contentbody">
<h1>Submit a patch</h1>
- <h2 id="high_level">High level:</h2>
+ <h2 id='high_level'>High level:</h2>
<p>The steps to submitting a patch for Wicket are:</p>
<ul>
<li>Identify an issue that you want to fix or improve</li>
-<li>Search <a href="https://issues.apache.org/jira/browse/WICKET">JIRA</a> and the mailing list to see if itâs already been discussed</li>
+<li>Search <a href='https://issues.apache.org/jira/browse/WICKET'>JIRA</a> and the mailing list to see if it’s already been discussed</li>
-<li>If itâs a bug or a feature request, open a <a href="https://issues.apache.org/jira/browse/WICKET">JIRA issue</a></li>
+<li>If it’s a bug or a feature request, open a <a href='https://issues.apache.org/jira/browse/WICKET'>JIRA issue</a></li>
-<li><a href="../start/quickstart.html">Create a quickstart</a> that you can use for prototyping the feature or demonstrating the bug</li>
+<li><a href='../start/quickstart.html'>Create a quickstart</a> that you can use for prototyping the feature or demonstrating the bug</li>
-<li>Attach this quickstart to the <a href="https://issues.apache.org/jira/browse/WICKET">JIRA issue</a> if itâs representing a bug report.</li>
+<li>Attach this quickstart to the <a href='https://issues.apache.org/jira/browse/WICKET'>JIRA issue</a> if it’s representing a bug report.</li>
-<li>Get <a href="http://git-scm.com/">Git</a> running</li>
+<li>Get <a href='http://git-scm.com/'>Git</a> running</li>
-<li><a href="../start/download.html#snapshots_and_latest_bleedingedge_code">Checkout out the code</a></li>
+<li><a href='../start/download.html#snapshots_and_latest_bleedingedge_code'>Checkout out the code</a></li>
<li>Make your changes</li>
@@ -201,7 +201,7 @@
<span class='go'>git diff --cached > /tmp/fix-WICKET-NNNN.patch</span>
</code></pre></div>
<ul>
-<li>Attach that file (/tmp/fix-WICKET-NNNN.patch) to the <a href="https://issues.apache.org/jira/browse/WICKET">JIRA</a></li>
+<li>Attach that file (/tmp/fix-WICKET-NNNN.patch) to the <a href='https://issues.apache.org/jira/browse/WICKET'>JIRA</a></li>
</ul>
</div>
<div id="clearer"></div>
Modified: wicket/common/site/trunk/_site/contribute/release.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/release.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/release.html (original)
+++ wicket/common/site/trunk/_site/contribute/release.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,33 +174,33 @@
<div id="contentbody">
<h1>Build a release</h1>
- <h2 id="contents">Contents</h2>
+ <h2 id='contents'>Contents</h2>
<ul>
-<li><a href="#release-60">Releasing Apache Wicket 6.x</a></li>
+<li><a href='#release-60'>Releasing Apache Wicket 6.x</a></li>
-<li><a href="#release-14">Releasing Apache Wicket 1.4.x+</a></li>
+<li><a href='#release-14'>Releasing Apache Wicket 1.4.x+</a></li>
-<li><a href="#release-13">Releasing Apache Wicket 1.3.x</a></li>
+<li><a href='#release-13'>Releasing Apache Wicket 1.3.x</a></li>
-<li><a href="#nexus">Staging Releases using the Apache Nexus Repository</a></li>
+<li><a href='#nexus'>Staging Releases using the Apache Nexus Repository</a></li>
-<li><a href="#announcing">Announcing the release</a></li>
+<li><a href='#announcing'>Announcing the release</a></li>
-<li><a href="#additional">Additional tasks</a></li>
+<li><a href='#additional'>Additional tasks</a></li>
</ul>
-<h2 id="release-60">Releasing Apache Wicket 6.x</h2>
+<h2 id='release-60'>Releasing Apache Wicket 6.x</h2>
-<p>Per <a href="http://apache.org/dev/release.html">Apache release policy</a> we need to build, vote on and release a source distribution. As a convenience to our users, we can also provide binary packages, that are uploaded to Maven Central, and a binary archive for folks that for whatever reason donât use Maven.</p>
+<p>Per <a href='http://apache.org/dev/release.html'>Apache release policy</a> we need to build, vote on and release a source distribution. As a convenience to our users, we can also provide binary packages, that are uploaded to Maven Central, and a binary archive for folks that for whatever reason don’t use Maven.</p>
-<h3 id="building_the_release">Building the Release</h3>
+<h3 id='building_the_release'>Building the Release</h3>
-<h4 id="required_software">Required software</h4>
+<h4 id='required_software'>Required software</h4>
<p>This assumes running a unix-y environment (i.e. OS X, Linux) and that you have the necessary tools installed, such as recent Maven, Java 6, gpg (-agent).</p>
-<h4 id="preparing">Preparing</h4>
+<h4 id='preparing'>Preparing</h4>
<ul>
<li>Pull changes</li>
@@ -210,7 +210,7 @@
<li>Update changelog and commit them</li>
</ul>
-<h4 id="building">Building</h4>
+<h4 id='building'>Building</h4>
<ul>
<li>Start gpg-agent as a daemon (OS X, using homebrew installation of gpg, gpg-agent, pinentry):</li>
@@ -218,7 +218,7 @@
<div class='highlight'><pre><code class='console'><span class='go'> eval `gpg-agent --daemon --pinentry-program /usr/local/bin/pinentry`</span>
</code></pre></div>
<ul>
-<li>Create an environment variable such that you can copy/paste several of the following commands (substitute 6.0.0 with the number youâre actually going to release)</li>
+<li>Create an environment variable such that you can copy/paste several of the following commands (substitute 6.0.0 with the number you’re actually going to release)</li>
<li>And create an environment variable for your Apache username for uploading the release:</li>
</ul>
@@ -252,7 +252,7 @@
<ul>
<li>Fill in NEWVERSION for all but the experimental submodules</li>
-<li>New development version doesnât matterâjust press enter, see next step</li>
+<li>New development version doesn’t matterâjust press enter, see next step</li>
<li>And running the following command:</li>
</ul>
@@ -272,9 +272,9 @@
<span class='go'>git archive --format=zip --prefix=apache-wicket-$NEWVERSION/ -o apache-wicket-$NEWVERSION.zip wicket-$NEWVERSION</span>
</code></pre></div>
<ul>
-<li><strong>NOTE 1</strong> the trailing â/â after âprefix=NEWVERSION is vital for the tarball</li>
+<li><strong>NOTE 1</strong> the trailing ’/’ after –prefix=NEWVERSION is vital for the tarball</li>
-<li><strong>NOTE 2</strong> you can ignore the gpg generated messages telling âYou need a passphrase to unlock the secret key forâ, unless an error occurredâthese messages are not error messages</li>
+<li><strong>NOTE 2</strong> you can ignore the gpg generated messages telling ‘You need a passphrase to unlock the secret key for’, unless an error occurred—these messages are not error messages</li>
<li>Sign the packages, the git tag and create the digests:</li>
</ul>
@@ -288,10 +288,12 @@
<p>To sign the tag (overwrites the maven generated tag), execute:</p>
<div class='highlight'><pre><code class='console'><span class='go'>git tag -s --force wicket-$NEWVERSION</span>
</code></pre></div>
-<h4 id="staging_the_build">Staging the build</h4>
-<div class='highlight'><pre><code class='console'><span class='go'>ssh $APACHEID@people.apache.org mkdir public_html/wicket-$NEWVERSION</span>
+<h4 id='staging_the_build'>Staging the build</h4>
+
+<p><div class='highlight'><pre><code class='console'><span class='go'>ssh $APACHEID@people.apache.org mkdir public_html/wicket-$NEWVERSION</span>
<span class='go'>scp apache-wicket-* $APACHEID@people.apache.org:public_html/wicket-$NEWVERSION</span>
-</code></pre></div>
+</code></pre></div></p>
+
<p>The step below uploads the artifacts to a staging area for Maven.</p>
<ul>
@@ -305,9 +307,9 @@
</code></pre></div>
<p>This will upload artifacts and signatures to Apache nexus in a staging repository.</p>
-<h4 id="create_a_binary_release">Create a binary release</h4>
+<h4 id='create_a_binary_release'>Create a binary release</h4>
-<p>As we donât vote on binary packages, but do want to cater to developers not using Maven, it is very convenient to create a download for non-Maven users.</p>
+<p>As we don’t vote on binary packages, but do want to cater to developers not using Maven, it is very convenient to create a download for non-Maven users.</p>
<p>The binary distribution should contain the same jar files that are uploaded to Maven Central. Unfortunately the Maven build creates duplicate jar files, but with different manifests (due to the inclusion of date/time of build), and the jar files have different signatures. Therefore it is necessary to create a distribution of the artifacts generated by the <code>mvn release:perform</code> command.</p>
@@ -333,32 +335,32 @@
</code></pre></div>
<p>This binary release contains all required files to comply with the release policy, and the binary artefacts generated by our Maven release build, including the experimental modules and examples.</p>
-<h4 id="vote_the_build">Vote the build</h4>
+<h4 id='vote_the_build'>Vote the build</h4>
<p>Start a vote on dev@ for this release. Allow for at least 72 hours, and ensure you take into account weekends.</p>
-<h4 id="promoting_the_build">Promoting the build</h4>
+<h4 id='promoting_the_build'>Promoting the build</h4>
-<p>When the vote has passed successfully (at least 3 binding +1âs) push the branch and the tag to Apache git:</p>
+<p>When the vote has passed successfully (at least 3 binding +1’s) push the branch and the tag to Apache git:</p>
<div class='highlight'><pre><code class='console'><span class='go'>git push origin build/wicket-$NEWVERSION:refs/heads/build/wicket-$NEWVERSION</span>
<span class='go'>git push -tags origin</span>
</code></pre></div>
-<p>You only need to do them if you havenât done so yet.</p>
+<p>You only need to do them if you haven’t done so yet.</p>
-<p>See also <a href="#nexus">managing nexus</a> for the steps needed to publish the artifacts to Maven Central. And donât forget to announce the release!</p>
+<p>See also <a href='#nexus'>managing nexus</a> for the steps needed to publish the artifacts to Maven Central. And don’t forget to announce the release!</p>
-<h2 id="release-14">Releasing Apache Wicket 1.4.x+</h2>
+<h2 id='release-14'>Releasing Apache Wicket 1.4.x+</h2>
-<h3 id="building_the_release_2">Building the Release</h3>
+<h3 id='building_the_release'>Building the Release</h3>
-<h4 id="preparing_2">Preparing</h4>
+<h4 id='preparing'>Preparing</h4>
<ul>
<li>Ask the dev@ mailing list if there are any issues that still need to be in the release (looking at JIRA is a good start)</li>
-<li><a href="https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/versions">Release</a> the version in JIRA</li>
+<li><a href='https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/versions'>Release</a> the version in JIRA</li>
-<li>Assuming there are none, and you are now in build mode, update the CHANGELOG-x.y file (you can use JIRA for this list: go to âreleasesâ, and under âunreleasedâ, next to your version, thereâs a release notes link)</li>
+<li>Assuming there are none, and you are now in build mode, update the CHANGELOG-x.y file (you can use JIRA for this list: go to “releases”, and under “unreleased”, next to your version, there’s a release notes link)</li>
</ul>
<p>Make sure your <code>~/.m2/settings.xml</code> contains the following definition</p>
@@ -374,9 +376,9 @@
<span class='go'></settings></span>
</code></pre></div>
<ul>
-<li>Make sure you have a GnuPG key which is added to <a href="https://svn.apache.org/repos/asf/wicket/common/KEYS">KEYS</a>. Read the header of KEYS file to see how to add it.</li>
+<li>Make sure you have a GnuPG key which is added to <a href='https://svn.apache.org/repos/asf/wicket/common/KEYS'>KEYS</a>. Read the header of KEYS file to see how to add it.</li>
-<li>Copy release-igor.sh script and modify any commands which donât match your environment (e.g. mvn5)</li>
+<li>Copy release-igor.sh script and modify any commands which don’t match your environment (e.g. mvn5)</li>
<li>Run ./release-mine.sh and enter the required input (new version, gpg passphrase, etc.). The script will create the build branch in Git, will upload the artifacts at Apache Nexus Staging repository and will copy the assemblies to your people.apache.org account.</li>
@@ -392,7 +394,7 @@
<span class='go'>chown -R :wicket /www/www.apache.org/dist/wicket/x.y.z</span>
</code></pre></div>
<ul>
-<li>Login to <a href="https://repository.apache.org">Apache Nexus Staging repo</a>, select the closed repository and click <strong>Release</strong>. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.</li>
+<li>Login to <a href='https://repository.apache.org'>Apache Nexus Staging repo</a>, select the closed repository and click <strong>Release</strong>. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.</li>
<li>If the release is voted down you can <strong>Drop</strong> the staged release and then restage later after incorporating the necessary changes.</li>
@@ -407,14 +409,14 @@
<li>Wait 24 hours until mirrors picked up release artifacts</li>
-<li>Announce (see <a href="#announcing">below</a>)</li>
+<li>Announce (see <a href='#announcing'>below</a>)</li>
</ul>
-<h2 id="nexus">Staging Releases using the Apache Nexus Staging Repository</h2>
+<h2 id='nexus'>Staging Releases using the Apache Nexus Staging Repository</h2>
-<p>The key to stage and manage repositories on <a href="https://repository.apache.org">Apache Nexus Staging repo</a> are your Apache Commiter credentials.</p>
+<p>The key to stage and manage repositories on <a href='https://repository.apache.org'>Apache Nexus Staging repo</a> are your Apache Commiter credentials.</p>
-<h3 id="staging_artifacts">Staging Artifacts</h3>
+<h3 id='staging_artifacts'>Staging Artifacts</h3>
<p><strong>Note</strong>: The steps below are part of release-igor.sh script!</p>
@@ -436,11 +438,11 @@
<span class='go'></servers></span>
<span class='go'></settings></span>
</code></pre></div>
-<p>This works if you can deploy artifacts into the repository.apache.org properly (i.e. you donât see failures mentioning 401 errors).</p>
+<p>This works if you can deploy artifacts into the repository.apache.org properly (i.e. you don’t see failures mentioning 401 errors).</p>
-<h3 id="managing_staged_artifacts">Managing Staged Artifacts</h3>
+<h3 id='managing_staged_artifacts'>Managing Staged Artifacts</h3>
-<p>By logging in with your Apache committer credentials to <a href="https://repository.apache.org">Apache Nexus Staging repo</a> you can access the management interface for the staged artifacts.</p>
+<p>By logging in with your Apache committer credentials to <a href='https://repository.apache.org'>Apache Nexus Staging repo</a> you can access the management interface for the staged artifacts.</p>
<p>The interface will allow you to:</p>
@@ -454,9 +456,9 @@
<li>Drop open and closed staging repositories.</li>
</ul>
-<p>More information is available at: <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven">Publishing Maven Artifacts</a></p>
+<p>More information is available at: <a href='http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven'>Publishing Maven Artifacts</a></p>
-<h2 id="announcing">Announcing the release</h2>
+<h2 id='announcing'>Announcing the release</h2>
<p>Edit the _config.yaml file. This file contains a site wide configuration section specific to Wicket:</p>
<div class='highlight'><pre><code class='yaml'><span class='l-Scalar-Plain'>wicket</span><span class='p-Indicator'>:</span>
@@ -464,7 +466,7 @@
<span class='l-Scalar-Plain'>released</span><span class='p-Indicator'>:</span> <span class='l-Scalar-Plain'>2010-08-11</span>
<span class='l-Scalar-Plain'>versions</span><span class='p-Indicator'>:</span> <span class='p-Indicator'>[</span><span class='nv'>1.3.7</span><span class='p-Indicator'>,</span> <span class='nv'>1.3-SNAPSHOT</span><span class='p-Indicator'>,</span> <span class='nv'>1.4.9</span><span class='p-Indicator'>,</span> <span class='nv'>1.4.10</span><span class='p-Indicator'>,</span> <span class='nv'>1.4-SNAPSHOT</span><span class='p-Indicator'>,</span> <span class='nv'>1.5-M1</span><span class='p-Indicator'>,</span> <span class='nv'>1.5-SNAPSHOT</span><span class='p-Indicator'>]</span>
</code></pre></div>
-<p>Youâll need to edit this part: modify the version, update the released date, and add the new version to the versions list (remove any stale releases, typically just leave the previous release as well).</p>
+<p>You’ll need to edit this part: modify the version, update the released date, and add the new version to the versions list (remove any stale releases, typically just leave the previous release as well).</p>
<ul>
<li>Write an announcement in the _posts directory</li>
@@ -476,10 +478,10 @@
<li>Misc. websites like javalobby, serverside, onjava etc.</li>
</ul>
-<h2 id="additional">Additional tasks</h2>
+<h2 id='additional'>Additional tasks</h2>
<ul>
-<li>Commit the JavaDocs to <a href="https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4">https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4</a> svnpubsub will push this directly to our website. (example script below)</li>
+<li>Commit the JavaDocs to <a href='https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4'>https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4</a> svnpubsub will push this directly to our website. (example script below)</li>
</ul>
<div class='highlight'><pre><code class='console'><span class='gp'>#</span> <span class='k'>do </span>this in your locally-checked-out release branch <span class='o'>(</span>i.e. svn.../releases/wicket-1.4.13<span class='o'>)</span>
<span class='go'>mvn javadoc:aggregate</span>
Modified: wicket/common/site/trunk/_site/contribute/write.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/write.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/write.html (original)
+++ wicket/common/site/trunk/_site/contribute/write.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,63 +174,63 @@
<div id="contentbody">
<h1>Write documentation</h1>
- <p>We use <a href="http://github.com/mojombo/jekyll">Jekyll</a> for writing our documentation on our main website. Publishing new content is as simple as regenerating the site and committing the changed files.</p>
+ <p>We use <a href='http://github.com/mojombo/jekyll'>Jekyll</a> for writing our documentation on our main website. Publishing new content is as simple as regenerating the site and committing the changed files.</p>
-<h2 id="contents">Contents</h2>
+<h2 id='contents'>Contents</h2>
<ul>
-<li><a href="#introduction">Introduction</a></li>
+<li><a href='#introduction'>Introduction</a></li>
-<li><a href="#install">Install Jekyll</a></li>
+<li><a href='#install'>Install Jekyll</a></li>
-<li><a href="#checkout">Check out from SVN</a></li>
+<li><a href='#checkout'>Check out from SVN</a></li>
-<li><a href="#run">Run the site</a></li>
+<li><a href='#run'>Run the site</a></li>
-<li><a href="#write">Write some documentation</a></li>
+<li><a href='#write'>Write some documentation</a></li>
-<li><a href="#update">Update the site</a></li>
+<li><a href='#update'>Update the site</a></li>
</ul>
-<h2 id="introduction">Introduction</h2>
+<h2 id='introduction'>Introduction</h2>
<p>The site is split into two parts: static content and the official Apache Wicket blog. The static content contains all the documentation that is more static (such as mailing lists, downloads, examples). The blog includes release announcements, adding new committers and other important Wicket related news.</p>
-<h2 id="install">Install Jekyll</h2>
+<h2 id='install'>Install Jekyll</h2>
-<p>Follow the instructions available on the <a href="http://github.com/mojombo/jekyll">Jekyll website</a>. Basically it boils down to:</p>
+<p>Follow the instructions available on the <a href='http://github.com/mojombo/jekyll'>Jekyll website</a>. Basically it boils down to:</p>
<div class='highlight'><pre><code class='console'><span class='go'>gem install jekyll</span>
</code></pre></div>
<p>You also need to install the Pygments Python module.</p>
-<h2 id="checkout">Check out from SVN</h2>
+<h2 id='checkout'>Check out from SVN</h2>
<p>Before you can edit the site, you need to check it out from SVN:</p>
<div class='highlight'><pre><code class='console'><span class='go'>svn co https://svn.apache.org/repos/asf/wicket/common/site/trunk wicket-site</span>
</code></pre></div>
-<h2 id="generate">Generating the site</h2>
+<h2 id='generate'>Generating the site</h2>
<p>You can regenerate the site in the checked out directory:</p>
<div class='highlight'><pre><code class='console'><span class='go'>./regenerate.sh</span>
</code></pre></div>
<p>Note that this script restores Subversion (<code>.svn</code>) subfolders inside <code>_site</code>, which are erased when Jekyll is generating the content.</p>
-<h2 id="run">Run the site</h2>
+<h2 id='run'>Run the site</h2>
<p>You can run the website and edit it live:</p>
<div class='highlight'><pre><code class='console'><span class='go'>./liveedit.sh</span>
</code></pre></div>
<p>This not only runs the server, but watches for modifications and regenerates any modified files.</p>
-<p>You can check out the website running at <a href="http://localhost:4000">localhost, port 4000</a>.</p>
+<p>You can check out the website running at <a href='http://localhost:4000'>localhost, port 4000</a>.</p>
-<h2 id="write">Write some documentation</h2>
+<h2 id='write'>Write some documentation</h2>
<p>Jekyll can render HTML from markdown syntax and textile syntax. <strong>For our site we use markdown</strong>.</p>
-<h3 id="page_template">Page template</h3>
+<h3 id='page_template'>Page template</h3>
-<p>Each page needs to have a YAML preamble that specifies the rendered template and other variables. If it doesnât include the YAML preamble, it wonât be rendered correctly.</p>
+<p>Each page needs to have a YAML preamble that specifies the rendered template and other variables. If it doesn’t include the YAML preamble, it won’t be rendered correctly.</p>
<p>Example preamble (includes the <code>---</code>):</p>
<div class='highlight'><pre><code class='yaml'><span class='nn'>---</span>
@@ -238,15 +238,15 @@
<span class='l-Scalar-Plain'>title</span><span class='p-Indicator'>:</span> <span class='l-Scalar-Plain'>Write documentation</span>
<span class='nn'>---</span>
</code></pre></div>
-<h3 id="syntax_highlighting">Syntax highlighting</h3>
+<h3 id='syntax_highlighting'>Syntax highlighting</h3>
<p>If you have a need to render code in your templates and have it syntax highlighted, surround the code with {\% highlight java \%} (substitute java with the language you want highlighted.)</p>
-<h3 id="menu">Menu</h3>
+<h3 id='menu'>Menu</h3>
<p>If you want your page linked from every page, include the link in <code>_includes/navigation.html</code>.</p>
-<h3 id="blog_posts">Blog posts</h3>
+<h3 id='blog_posts'>Blog posts</h3>
<p>For news items such as release announcements, new committers and other happenings, it is appriorate to create a blog post. The blog post is automatically added to the front page and the RSS feed.</p>
@@ -256,9 +256,9 @@
<span class='l-Scalar-Plain'>title</span><span class='p-Indicator'>:</span> <span class='l-Scalar-Plain'>Wicket 1.4.7 released</span>
<span class='nn'>---</span>
</code></pre></div>
-<h2 id="update">Update the site</h2>
+<h2 id='update'>Update the site</h2>
-<p>When youâre done with making your changes, please check the following:</p>
+<p>When you’re done with making your changes, please check the following:</p>
<ul>
<li>Do the modified files contain only those changes that you actually want to publish? (Use <code>svn diff</code> to check)</li>
@@ -266,7 +266,7 @@
<li>Did you restart Jekyll to generate the site?</li>
</ul>
-<p>If these things are OK, you can either <a href="patch.html">generate a patch</a> when youâre not a committer, or just commit the changes. In the latter case, the modifications are pushed immediately to the site and are live within a minute.</p>
+<p>If these things are OK, you can either <a href='patch.html'>generate a patch</a> when you’re not a committer, or just commit the changes. In the latter case, the modifications are pushed immediately to the site and are live within a minute.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/doap.rdf
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/doap.rdf?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/doap.rdf (original)
+++ wicket/common/site/trunk/_site/doap.rdf Sat Apr 26 20:03:27 2014
@@ -25,8 +25,8 @@
<release>
<Version>
<name>Latest Stable Release</name>
- <created>2014-02-21</created>
- <revision>6.14.0</revision>
+ <created>2014-04-23</created>
+ <revision>6.15.0</revision>
</Version>
</release>
<repository>
Modified: wicket/common/site/trunk/_site/dtds.data/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/dtds.data/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/dtds.data/index.html (original)
+++ wicket/common/site/trunk/_site/dtds.data/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -179,11 +179,11 @@
<p>These definitions are not used by Wicket for its internal working but you can use them in your HTML/XML editor to simplify the development of your pages/panels markup.</p>
<ul>
-<li><a href="wicket-xhtml1.3-strict.dtd">Wicket 1.3 DTD</a></li>
+<li><a href='wicket-xhtml1.3-strict.dtd'>Wicket 1.3 DTD</a></li>
-<li><a href="wicket-xhtml1.4-strict.dtd">Wicket 1.4 DTD</a></li>
+<li><a href='wicket-xhtml1.4-strict.dtd'>Wicket 1.4 DTD</a></li>
-<li><a href="http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=blob_plain;f=wicket-core/src/main/resources/META-INF/wicket-1.5.xsd;hb=master">Wicket 1.5 XSD</a></li>
+<li><a href='http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=blob_plain;f=wicket-core/src/main/resources/META-INF/wicket-1.5.xsd;hb=master'>Wicket 1.5 XSD</a></li>
</ul>
</div>
<div id="clearer"></div>
Modified: wicket/common/site/trunk/_site/help/email.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/email.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/email.html (original)
+++ wicket/common/site/trunk/_site/help/email.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -179,14 +179,14 @@
<ul>
<li>The <strong>announcements</strong> mailing list for announcing new releases and other important Wicket news.</li>
-<li>The <strong>users</strong> mailing list for developers working with Wicket&emdash;that would be if youâre using Wicket or are interested in using it</li>
+<li>The <strong>users</strong> mailing list for developers working with Wicket&emdash;that would be if you’re using Wicket or are interested in using it</li>
<li>The <strong>dev</strong> mailing list for talking about development of Wicket itself. If you doubt that your message belongs on this list, use the <strong>users</strong> list.</li>
<li>Thereâs also a <strong>commits</strong> mailing list for following SVN commits and JIRA issues.</li>
</ul>
-<h2 id="subscribing_and_unsubscribing">Subscribing and unsubscribing</h2>
+<h2 id='subscribing_and_unsubscribing'>Subscribing and unsubscribing</h2>
<table>
<tr>
<td>Announcements list</td>
@@ -225,9 +225,9 @@
<td><a href='mailto:commits-help@wicket.apache.org?subject=Help for Apache Wicket commits list'>Help</a></td>
</tr>
</table>
-<h2 id="report_a_security_issue">Report a security issue</h2>
+<h2 id='report_a_security_issue'>Report a security issue</h2>
-<p>If you have a security issue to report, please contact the <a href="mailto:private@wicket.apache.org?Security">Wicket PMC</a>.</p>
+<p>If you have a security issue to report, please contact the <a href='mailto:private@wicket.apache.org?Security'>Wicket PMC</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/help/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/index.html (original)
+++ wicket/common/site/trunk/_site/help/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -182,21 +182,21 @@
<li>Commercial Support</li>
</ol>
-<h2 id="support_from_the_apache_wicket_open_source_project">Support From the Apache Wicket Open Source Project</h2>
+<h2 id='support_from_the_apache_wicket_open_source_project'>Support From the Apache Wicket Open Source Project</h2>
<p>If you are experiencing problems using Wicket please report your problem via the Issue Tracker. You may also find it useful to discuss your issues with the community on one of the Mailing Lists. Below are some resources to check before asking for help:</p>
<ul>
-<li><a href="email.html">Mailing Lists</a></li>
+<li><a href='email.html'>Mailing Lists</a></li>
-<li><a href="https://issues.apache.org/jira/browse/WICKET">Issue Tracker</a></li>
+<li><a href='https://issues.apache.org/jira/browse/WICKET'>Issue Tracker</a></li>
-<li><a href="irc://irc.freenode.net/%23%23wicket">IRC</a></li>
+<li><a href='irc://irc.freenode.net/%23%23wicket'>IRC</a></li>
</ul>
-<p>Before asking for help with your issue, itâs a very good idea to search for your issue in the mailing list archives and the FAQ. The majority of issues can be solved in this manner without having to send an email to the mailing list. If you donât find an answer, use the guidelines below when writing the e-mail.</p>
+<p>Before asking for help with your issue, it’s a very good idea to search for your issue in the mailing list archives and the FAQ. The majority of issues can be solved in this manner without having to send an email to the mailing list. If you don’t find an answer, use the guidelines below when writing the e-mail.</p>
-<h3 id="how_to_get_help">How to Get Help</h3>
+<h3 id='how_to_get_help'>How to Get Help</h3>
<p>Whenever you are reporting a problem, please be sure to include as much information as possible; the more we know, the better the chance of a quicker resolution.</p>
@@ -212,21 +212,21 @@
<li>log output can be useful too; sometimes enabling DEBUG logging can help your code & configuration files are often useful</li>
</ul>
-<h3 id="how_to_get_help_faster">How to get help faster</h3>
+<h3 id='how_to_get_help_faster'>How to get help faster</h3>
<p>We can help you much quicker if you try the following</p>
<ul>
-<li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think youâve found a bug, can you create a test case to demonstrate the bug?</li>
+<li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you’ve found a bug, can you create a test case to demonstrate the bug?</li>
<li>submit a patch fixing the bug! (We also buy you beer when we meet you if you submit bug fixes for memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if its huge) to the JIRA we can normally fix things much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory leaks its quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out whats wrong from that.</li>
</ul>
-<h2 id="commercial_support">Commercial Support</h2>
+<h2 id='commercial_support'>Commercial Support</h2>
-<p>The list of companies found at <a href="https://cwiki.apache.org/confluence/display/WICKET/Companies+that+provide+services">this wiki page</a> provide commercial services for Wicket which ranges from training courses, consultancy and even project development.</p>
+<p>The list of companies found at <a href='https://cwiki.apache.org/confluence/display/WICKET/Companies+that+provide+services'>this wiki page</a> provide commercial services for Wicket which ranges from training courses, consultancy and even project development.</p>
-<p>Being mentioned here is not an indication of official âendorsementâ by the Apache Software Foundation, but is instead provided as a public service. This list is in no way a complete listing of the many organizations providing either free or for cost support for ASF projects. If you would like to be added to this list, or removed, sign up for the wiki and add yourself to the list.</p>
+<p>Being mentioned here is not an indication of official “endorsement” by the Apache Software Foundation, but is instead provided as a public service. This list is in no way a complete listing of the many organizations providing either free or for cost support for ASF projects. If you would like to be added to this list, or removed, sign up for the wiki and add yourself to the list.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/help/irc.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/irc.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/irc.html (original)
+++ wicket/common/site/trunk/_site/help/irc.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/help/reportabug.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/reportabug.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/reportabug.html (original)
+++ wicket/common/site/trunk/_site/help/reportabug.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,39 +174,39 @@
<div id="contentbody">
<h1>Report a bug</h1>
- <p>Wicket manages bug reports via the <a href="http://issues.apache.org/jira/browse/WICKET">Apache Jira site</a></p>
+ <p>Wicket manages bug reports via the <a href='http://issues.apache.org/jira/browse/WICKET'>Apache Jira site</a></p>
-<p>It requires you to register with the site, to avoid spamming, and attribute credit where its due. Itâs relatively painless. Much harder is writing a clear and concise bug report.</p>
+<p>It requires you to register with the site, to avoid spamming, and attribute credit where its due. It’s relatively painless. Much harder is writing a clear and concise bug report.</p>
<p>Etiquette for a bug report is:</p>
<ol>
-<li><strong>Always search for an existing bug report about the issue before adding your own.</strong> This can be tricky, but several duplicate bug reports just cause an administration headache for developers. If in doubt you can always post the details of the bug to the <a href="email.html">mailing list</a>, and wait to be asked to submit a bug report by a dev. But the jira search functionality is pretty good, so do have go.</li>
+<li><strong>Always search for an existing bug report about the issue before adding your own.</strong> This can be tricky, but several duplicate bug reports just cause an administration headache for developers. If in doubt you can always post the details of the bug to the <a href='email.html'>mailing list</a>, and wait to be asked to submit a bug report by a dev. But the jira search functionality is pretty good, so do have go.</li>
<li><strong>Be clear and concise in your language.</strong> Wording a short but useful summary, with a description that contains all the steps leading up to the error plus any extra circumstantial evidence, is not always easy, but its vital to getting the issue resolved, and really valuable.</li>
<li><strong>Watch the bug.</strong> The developers may ask you for more information via the issue comments, so its good practices to check in on the issue whilst its still open.</li>
-<li><strong>Donât be shy of maintaining the issue.</strong> If you find its a duplicate of some other issue that was reported before yours, then mark it as a duplicate, and watch the original. If you get more info on the bug, add it as a comment. If it doesnt get noticed by a dev, try submitting a quickstart or better still a patch. Ask for it to be reviewed via the mailing list.</li>
+<li><strong>Don’t be shy of maintaining the issue.</strong> If you find its a duplicate of some other issue that was reported before yours, then mark it as a duplicate, and watch the original. If you get more info on the bug, add it as a comment. If it doesnt get noticed by a dev, try submitting a quickstart or better still a patch. Ask for it to be reviewed via the mailing list.</li>
</ol>
-<p>You will be rewarded with <a href="https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=-1&issueStatus=all&selectedProjectId=12310561&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next">subtle kudos</a> and the bug is much more likely to be fixed promptly.</p>
+<p>You will be rewarded with <a href='https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=-1&issueStatus=all&selectedProjectId=12310561&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next'>subtle kudos</a> and the bug is much more likely to be fixed promptly.</p>
-<h2 id="build_a_quickstart">Build a Quickstart</h2>
+<h2 id='build_a_quickstart'>Build a Quickstart</h2>
-<p>See <a href="/start/quickstart.html">getting started</a> for a good introduction to building a barebone Wicket project from one command. There is even a tool to let you customise the command for your project.</p>
+<p>See <a href='/start/quickstart.html'>getting started</a> for a good introduction to building a barebone Wicket project from one command. There is even a tool to let you customise the command for your project.</p>
-<p>Or you can watch Al Mawâs excellent <a href="http://herebebeasties.com/2007-10-07/wicket-quickstart">screencast</a> covering the whole process of installing and running Maven, and getting your Eclipse workspace set up.</p>
+<p>Or you can watch Al Maw’s excellent <a href='http://herebebeasties.com/2007-10-07/wicket-quickstart'>screencast</a> covering the whole process of installing and running Maven, and getting your Eclipse workspace set up.</p>
<p>The Maven command provided there is the quickest way to get a working Wicket project that you can use to clearly demonstrate a bug.</p>
<p>Once you have an example that shows the minimum conditions under which the issue occurs, then you can zip up the project and attach it to the relevant issue.</p>
-<p>When a Wicket dev <a href="https://issues.apache.org/jira/browse/WICKET-497?focusedCommentId=12521870&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12521870">asks you to submit a quickstart</a>, that is what they mean.</p>
+<p>When a Wicket dev <a href='https://issues.apache.org/jira/browse/WICKET-497?focusedCommentId=12521870&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12521870'>asks you to submit a quickstart</a>, that is what they mean.</p>
-<p>That is far more useful than posting reams of your application code and telling everyone it doesnât work. The former will help diagnose the problem, the latter will mainly get you abused on the mailing list.</p>
+<p>That is far more useful than posting reams of your application code and telling everyone it doesn’t work. The former will help diagnose the problem, the latter will mainly get you abused on the mailing list.</p>
-<h2 id="submit_a_patch">Submit a patch</h2>
+<h2 id='submit_a_patch'>Submit a patch</h2>
<p>This is the most involved, but the most rewarding route ;-). In a nutshell this involves:</p>
@@ -220,25 +220,25 @@
<li>Submitting your fix as a Subversion patch file.</li>
</ul>
-<p>This guide will outline how to do it with Eclipse + Subclipse + m2eclipse. If you prefer the command line, then start here: <a href="/contribute/build.html">building from source</a> If you can provide a walk through for your IDE of choice then please do add it.</p>
+<p>This guide will outline how to do it with Eclipse + Subclipse + m2eclipse. If you prefer the command line, then start here: <a href='/contribute/build.html'>building from source</a> If you can provide a walk through for your IDE of choice then please do add it.</p>
-<h3 id="setting_up">Setting up</h3>
+<h3 id='setting_up'>Setting up</h3>
<p>Using an Eclipse 3.4.x flavour of your choice add install the following plugins</p>
<ul>
-<li><a href="http://subclipse.tigris.org/">Subclipse for accessing Subversion</a> - Eclipse update site URL http://subclipse.tigris.org/update_1.6.x</li>
+<li><a href='http://subclipse.tigris.org/'>Subclipse for accessing Subversion</a> - Eclipse update site URL http://subclipse.tigris.org/update_1.6.x</li>
-<li><a href="http://m2eclipse.sonatype.org/">m2eclipse for maven support</a> - Eclipse update site: http://m2eclipse.sonatype.org/update/</li>
+<li><a href='http://m2eclipse.sonatype.org/'>m2eclipse for maven support</a> - Eclipse update site: http://m2eclipse.sonatype.org/update/</li>
</ul>
-<p>I usually install the entire Subclipse plugin, and all of m2eclipse except the Project configurators unless I am using a J2EE version of Eclipse. I had a spurious error when adding the m2eclipse update site, âNo repository found at http://www.md.pp.ru/~eu/12/â but it didnât cause any problems with the install.</p>
+<p>I usually install the entire Subclipse plugin, and all of m2eclipse except the Project configurators unless I am using a J2EE version of Eclipse. I had a spurious error when adding the m2eclipse update site, “No repository found at http://www.md.pp.ru/~eu/12/” but it didn’t cause any problems with the install.</p>
-<h3 id="checking_out_wicket_from_subversion">Checking out Wicket from Subversion</h3>
+<h3 id='checking_out_wicket_from_subversion'>Checking out Wicket from Subversion</h3>
<ul>
<li>
-<p><strong>Add the Wicket Subversion repository</strong> - Navigate to Window > Show Perspective > Other⦠> SVN Repository Exploring (eclipse uses the term perspective to mean a collection of views, and a view is one single panel with some specific function like the navigator view or the editor view) In the SVN Repositories tab on the left, right click > New > Repository Location⦠and paste in the repository url: http://svn.apache.org/repos/asf/wicket</p>
+<p><strong>Add the Wicket Subversion repository</strong> - Navigate to Window > Show Perspective > Other… > SVN Repository Exploring (eclipse uses the term perspective to mean a collection of views, and a view is one single panel with some specific function like the navigator view or the editor view) In the SVN Repositories tab on the left, right click > New > Repository Location… and paste in the repository url: http://svn.apache.org/repos/asf/wicket</p>
</li>
<li>
@@ -252,11 +252,11 @@
</li>
<li>
-<p><strong>Building Wicket</strong> - All that waiting wasnât in vain, as you should now have a fully checked out, dependency managed, built, possibly working, Wicket code base.</p>
+<p><strong>Building Wicket</strong> - All that waiting wasn’t in vain, as you should now have a fully checked out, dependency managed, built, possibly working, Wicket code base.</p>
</li>
</ul>
-<h3 id="kick_the_tires">Kick the tires</h3>
+<h3 id='kick_the_tires'>Kick the tires</h3>
<ul>
<li>Create a Quickstart via the wicket-archetype-quickstart</li>
@@ -265,7 +265,7 @@
<li>Set version element to the same value as the one found in the Wicket project pom.xml (e.g. 1.4-SNAPSHOT)</li>
-<li>The plugin should automagically resolve the quickstartâs Wicket dependency from the project rather than a .jar</li>
+<li>The plugin should automagically resolve the quickstart’s Wicket dependency from the project rather than a .jar</li>
<li>Find WicketApplication.java</li>
@@ -274,33 +274,29 @@
<li>If all is well, you should be taken to the Wicket project .java version of WebApplication rather than a .class file from a .jar</li>
</ul>
-<h3 id="proving_a_bug_exists">Proving a bug exists</h3>
+<h3 id='proving_a_bug_exists'>Proving a bug exists</h3>
<ul>
<li><strong>Writing a unit test with WicketTester</strong></li>
</ul>
-<h3 id="submitting_a_patch">Submitting a patch</h3>
+<h3 id='submitting_a_patch'>Submitting a patch</h3>
<ul>
<li>
-<p><strong>Extract your changeset into a patch file</strong> - As we donât all have commit access to the svn repository, we need some other way of getting our changes to the developers. This is done by making an svn patch file, essentially a plain text diff, with some subversion specific formatting. With the Subclipse plug-in creating a patch file is as simple as:</p>
+<p><strong>Extract your changeset into a patch file</strong> - As we don’t all have commit access to the svn repository, we need some other way of getting our changes to the developers. This is done by making an svn patch file, essentially a plain text diff, with some subversion specific formatting. With the Subclipse plug-in creating a patch file is as simple as:</p>
<ol>
<li>Right click on the project root (e.g. wicket)</li>
<li>
-<blockquote>
-<p>Team > Create Patch</p>
-</blockquote>
+<p>Team > Create Patch…</p>
</li>
-<li>Save In File System (and provide a filename, of the form <strong>WICKET-<bug id number>-fix.patch</strong>)</li>
+<li>Save In File System (and provide a filename, of the form <strong>WICKET-<bug id number>-fix.patch</strong>)</li>
<li>
-<blockquote>
<p>Next ></p>
-</blockquote>
</li>
<li>Patch Root: Project</li>
Modified: wicket/common/site/trunk/_site/help/security.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/security.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/security.html (original)
+++ wicket/common/site/trunk/_site/help/security.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/help/support.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/help/support.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/help/support.html (original)
+++ wicket/common/site/trunk/_site/help/support.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/index.html (original)
+++ wicket/common/site/trunk/_site/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -177,82 +177,86 @@
<p>With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML.</p>
<ul>
-<li>Check the <a href="meet/features.html">feature list</a></li>
+<li>Check the <a href='meet/features.html'>feature list</a></li>
-<li>Read some <a href="meet/buzz.html">Wicket buzz</a>, some <a href="meet/blogs.html">Wicket blogs</a></li>
+<li>Read some <a href='meet/buzz.html'>Wicket buzz</a>, some <a href='meet/blogs.html'>Wicket blogs</a></li>
-<li>Find out why you should <a href="meet/introduction.html">use Wicket</a></li>
+<li>Find out why you should <a href='meet/introduction.html'>use Wicket</a></li>
-<li>Check out some selected <a href="learn/examples">examples in detail</a> or see them and many more in <a href="http://www.wicket-library.com/wicket-examples/">live action</a></li>
+<li>Check out some selected <a href='learn/examples'>examples in detail</a> or see them and many more in <a href='http://www.wicket-library.com/wicket-examples/'>live action</a></li>
-<li>Take a look at our live <a href="http://www.wicket-library.com/wicket-examples/compref/">component reference</a></li>
+<li>Take a look at our live <a href='http://www.wicket-library.com/wicket-examples/compref/'>component reference</a></li>
-<li>Go and <a href="start/download.html">download Wicket</a></li>
+<li>Go and <a href='start/download.html'>download Wicket</a></li>
-<li>See what <a href="learn/projects">extras are available</a></li>
+<li>See what <a href='learn/projects'>extras are available</a></li>
</ul>
-<p>Wicket is released under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, Version 2.0</a>.</p>
+<p>Wicket is released under the <a href='http://www.apache.org/licenses/LICENSE-2.0.html'>Apache License, Version 2.0</a>.</p>
-<h1 id="cve20140043__apache_wicket_information_disclosure_vulnerability"><a href="/2014/02/21/cve-2014-0043.html">CVE-2014-0043 - Apache Wicket Information disclosure vulnerability</a></h1>
-<p>Vendor: The Apache Software Foundation</p><p>Versions Affected: Apache Wicket 1.5.10 and 6.13.0</p><p>Description:</p><p>By issuing requests to special urls handled by Wicket it is possible to check for the existence of particular classes in the classpath and thus check whether a third party library with a known security vulnerability is in use.</p><p>The application developers are recommended to upgrade to:</p><ul>
-<li><a href='/2014/02/06/wicket-1.5.11-released.html'>Apache Wicket 1.5.11</a></li>
-
-<li><a href='/2014/02/20/wicket-6.14.0-released.html'>Apache Wicket 6.14.0</a></li>
-</ul><p>Credit: This issue was reported by Christian Schneider!</p><p>Apache Wicket Team</p>
-<h1 id="apache_wicket_6140_released"><a href="/2014/02/20/wicket-6.14.0-released.html">Apache Wicket 6.14.0 released</a></h1>
-<p>The Apache Wicket PMC is proud to announce Apache Wicket 6.14.0!</p><p>This release marks the fourteenth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0.</p><h3 id='new_and_noteworthy'>New and noteworthy</h3><p>This release fixes 34 bugs and adds the following improvements:</p><ul>
-<li>JQuery upgraded from 1.10.2 to 1.11.0</li>
-
-<li>Fix for <a href='/2014/02/21/cve-2014-0043.html'>CVE-2014-0043</a></li>
-
-<li>Wicket Session may not be saved in the SessionStore (Http Session) under some conditions and lead to lost state</li>
-
-<li>Update classes copied from commons-fileupload to fix CVE-2014-0050</li>
+<h1 id='apache_wicket_6150_released'><a href='/2014/04/23/wicket-6.15.0-released.html'>Apache Wicket 6.15.0 released</a></h1>
+<p>The Apache Wicket PMC is proud to announce Apache Wicket 6.15.0!</p><p>This release marks the fifteenth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0.</p><h3 id='new_and_noteworthy'>New and noteworthy</h3><p>This release fixes 25 bugs and adds the following improvements:</p><ul>
+<li>The second level page store has been disabled by default (see issue <a href='https://issues.apache.org/jira/browse/WICKET-5554'>WICKET-5554</a> for more details).</li>
-<li>Allow <script> tags to have children components to be able to use client side templating</li>
-</ul><h3 id='using_this_release'>Using this release</h3><p>With Apache Maven update your dependency to (and donât forget to update any other dependencies on Wicket projects to the same version):</p><div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
+<li>Created new placeholder tag to indicate where header contributions should appear. See this <a href='http://wicketinaction.com/2014/03/header-contributions-positioning/'>blog post entry</a> or paragraph 15.8 of the official guide.</li>
+</ul><p>This release also celebrates the 10th birthday of Wicket!</p><h3 id='using_this_release'>Using this release</h3><p>With Apache Maven update your dependency to (and don’t forget to update any other dependencies on Wicket projects to the same version):</p><div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
<span class='nt'><groupId></span>org.apache.wicket<span class='nt'></groupId></span>
<span class='nt'><artifactId></span>wicket-core<span class='nt'></artifactId></span>
- <span class='nt'><version></span>6.14.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.15.0<span class='nt'></version></span>
<span class='nt'></dependency></span>
</code></pre></div><p>Or download and build the distribution yourself, or use our convenience binary package</p><ul>
-<li>Source: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.14.0'>http://www.apache.org/dyn/closer.cgi/wicket/6.14.0</a></li>
+<li>Source: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.15.0'>http://www.apache.org/dyn/closer.cgi/wicket/6.15.0</a></li>
-<li>Binary: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.14.0/binaries'>http://www.apache.org/dyn/closer.cgi/wicket/6.14.0/binaries</a></li>
+<li>Binary: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.15.0/binaries'>http://www.apache.org/dyn/closer.cgi/wicket/6.15.0/binaries</a></li>
</ul><h3 id='upgrading_from_earlier_versions'>Upgrading from earlier versions</h3><p>If you upgrade from 6.y.z this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at</p><ul>
<li><a href='https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0'>Migration to Wicket 6.0</a></li>
-</ul><p>Have fun!</p><p>â The Wicket team</p><h3 id='release_notes__wicket__version_6140'>Release Notes - Wicket - Version 6.14.0</h3><h4 id='bug'>Bug</h4><pre><code>* [WICKET-4697] - Autolinking not working as soon as component gets a wicket:id
-* [WICKET-5043] - Page not mounted with WebApplication#mountPackage
-* [WICKET-5449] - Missing chapter 2 is causing off-by-one page names in the guides URL links
-* [WICKET-5460] - onBeforeRender called too early on stateless page
-* [WICKET-5462] - Ajax form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton
-* [WICKET-5464] - AbstractAjaxTimerBehavior does not work in combination with Wizards
-* [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws ComponentNotFoundException as a side-effect
-* [WICKET-5467] - NumberTextField should support "any" as valid step attribute value
-* [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends "/" after query parameters
-* [WICKET-5469] - ModalWindow unload warning always displayed (even if window is closed)
-* [WICKET-5472] - PackageResource#internalGetResourceStream() should return ProcessingResourceStream only when the resource is existing
-* [WICKET-5473] - Wicket does not handle non in-memory Httpsessions correctly
-* [WICKET-5477] - CSS class is not applied to <TD> for data filter
-* [WICKET-5478] - Wrong JavaDoc for WicketTester
-* [WICKET-5480] - AutoLabelResolver creates null pointer exception in 6.13
-* [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named annotations
-* [WICKET-5484] - WebPageRenderer must not render full page in Ajax requests
-* [WICKET-5486] - WebPageRenderer should honor RedirectPolicy.ALWAYS_REDIRECT more consistently
-* [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning undefined on IE8, positions calendar out of viewport
-* [WICKET-5492] - WebApplication ignores a SecurityException when reading the configuration type
-* [WICKET-5496] - Wrong translation of RangeValidator.minimum and RangeValidator.maximum
-* [WICKET-5497] - NPE in JsonUtils when the value is null
-* [WICKET-5499] - Page is not touched during initialization
-* [WICKET-5500] - Ignore the path parameters when reading the page class
-* [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050</code></pre><h4 id='improvement'>Improvement</h4><pre><code>* [WICKET-5288] - Allow &lt;script&gt;-Tags act as WebMarkUpContainer to add Child-Components
-* [WICKET-5439] - Allow restarting AbstractAjaxTimerBehavior without updating its hosting component
-* [WICKET-5463] - RequestUtil.getCharset(HttpServletRequest request) Resilience against unsupported Charsets in Request
-* [WICKET-5470] - Remove 'final' from org.apache.wicket.markup.html.form.EnumChoiceRenderer#getDisplayValue
-* [WICKET-5471] - Store the page if it is known that it will be used in a following request
-* [WICKET-5493] - Disable jar indexing</code></pre><h4 id='new_feature'>New Feature</h4><pre><code>* [WICKET-3491] - Introduce IComponentOnConfigureListener</code></pre><h4 id='task'>Task</h4><pre><code>* [WICKET-5488] - Promote experimental modules to become stable
-* [WICKET-5494] - Upgrade JQuery to latest stable - 1.11.0 and 2.1.0</code></pre><h1>Older news items</h1><ul>
+</ul><p>Have fun!</p><p>â The Wicket team</p><h3 id='release_notes__wicket__version_6150'>Release Notes - Wicket - Version 6.15.0</h3><h4 id='subtask'>Sub-task</h4><pre><code>* [WICKET-5510] - Avoid using jQuery.text() when possible. It is very slow in IE
+* [WICKET-5554] - Disable second level pages store because it is efficient only when manually configured</code></pre><h4 id='bug'>Bug</h4><pre><code>* [WICKET-5243] - JS: High stack size in Function Executor causes "too much recursion"
+* [WICKET-5284] - Too deep recursion in AbstractHierarchyIterator
+* [WICKET-5504] - AjaxRequestTarget.append/prependJavaScript cannot handle scripts with new-lines anymore
+* [WICKET-5505] - DefaultPropertyResolver does not respect JavaBean conventions
+* [WICKET-5506] - DefaultPropertyResolver should resolve the Property according to the getter first
+* [WICKET-5509] - Wicket examples' MailTemplate from Page is broken
+* [WICKET-5517] - IE11 returns false for Wicket.Browser.isIE()
+* [WICKET-5518] - FormComponent.updateCollectionModel does not handle unmodifiableList
+* [WICKET-5521] - Stateless forms does not work when RecreateMountedPagesAfterExpiry turned off
+* [WICKET-5522] - Failing HTTPS redirect to RequireHttps annotated pages with ONE_PASS_RENDER strategy
+* [WICKET-5523] - Ajax indicator not working when display is set to none in css
+* [WICKET-5532] - NPE calling PackageResource.getResourceStream() if there is no RequestCycle defined
+* [WICKET-5534] - DataTable component must throw an exception when attached to non-&lt;table&gt; element
+* [WICKET-5536] - Error message without parmeters filled.
+* [WICKET-5537] - Wicket.DOM.toggleClass is called with additional "#" inside AutoLabelResolver
+* [WICKET-5541] - NullPointerException in SubscribeAnnotationEventSubscriptionInvoker on remove of component from page
+* [WICKET-5545] - Cannot use redirect in ModalWindow's page#onInitialize()
+* [WICKET-5546] - Adding behavior in component instantiation listener causes Page.onInitialize() being called even if constructor throws an exception
+* [WICKET-5547] - Javadoc for ReuseIfModelsEqualStrategy should mention that models must implement hashCode() method
+* [WICKET-5548] - Websocket initialization URL is not valid when filter is not mapped to root.
+* [WICKET-5555] - AbstractAutoCompleteBehavior.WrappedHeaderItem should depend on wicket-ajax.js
+* [WICKET-5556] - Error in wicket-autocomplete.js bad reference of $
+* [WICKET-5557] - Don't cache the result of AuthenticatedWebApplication#getWebSessionClass()
+* [WICKET-5558] - Autolinking does not always work in inheritted markup
+* [WICKET-5561] - Derived page without own markup leads to MarkupNotFoundException when BasePage has &lt;wicket:head&gt; in its markup</code></pre><h4 id='improvement'>Improvement</h4><pre><code>* [WICKET-5508] - Memory model improvements for Session fields
+* [WICKET-5512] - Allow using child selector for JS event bindings
+* [WICKET-5520] - improve reusability of DataTable and AbstractPageableView
+* [WICKET-5528] - Allow models of subtypes of Select type parameter in SelectOption constructor
+* [WICKET-5529] - Add WebSocketBehavior/Resource#onPush() callback method
+* [WICKET-5531] - Create new placeholder tag to indicate where header contributions should appear
+* [WICKET-5538] - When using Component.setDefaultModel, only detach the previous model if the new one is different
+* [WICKET-5549] - continueToOriginalDestination() fails after redirectToInterceptPage() on AjaxRequest* [WICKET-5288] - Allow &amp;lt;script&amp;gt;-Tags act as WebMarkUpContainer to add Child-Components</code></pre><h4 id='new_feature'>New Feature</h4><pre><code>* [WICKET-831] - Return response status 404 when a mapper cannot decode a request url
+* [WICKET-2542] - Provide ajax buttons for wizard</code></pre><h4 id='task'>Task</h4><pre><code>* [WICKET-5514] - Update Wicket fragment example</code></pre><h4 id='wish'>Wish</h4><pre><code>* [WICKET-5516] - RadioChoice / add a getAdditionalAttributes() also for <label>-tag
+* [WICKET-5542] - Remove final from TextArea.onComponentTagBody()</code></pre>
+<h1 id='cve20140043__apache_wicket_information_disclosure_vulnerability'><a href='/2014/02/21/cve-2014-0043.html'>CVE-2014-0043 - Apache Wicket Information disclosure vulnerability</a></h1>
+<p>Vendor: The Apache Software Foundation</p><p>Versions Affected: Apache Wicket 1.5.10 and 6.13.0</p><p>Description:</p><p>By issuing requests to special urls handled by Wicket it is possible to check for the existence of particular classes in the classpath and thus check whether a third party library with a known security vulnerability is in use.</p><p>The application developers are recommended to upgrade to:</p><ul>
+<li><a href='/2014/02/06/wicket-1.5.11-released.html'>Apache Wicket 1.5.11</a></li>
+
+<li><a href='/2014/02/20/wicket-6.14.0-released.html'>Apache Wicket 6.14.0</a></li>
+</ul><p>Credit: This issue was reported by Christian Schneider!</p><p>Apache Wicket Team</p><h1>Older news items</h1><ul>
+
+
+<li>
+ <a href='/2014/02/20/wicket-6.14.0-released.html'>Apache Wicket 6.14.0 released</a> - <span>20 Feb 2014</span><br />
+ The Apache Wicket PMC is proud to announce Apache Wicket 6.14.0! This release marks the fourteenth minor release of Wicket 6. Starting with Wicket 6...
+ <a href='/2014/02/20/wicket-6.14.0-released.html'>more</a></li>
<li>
@@ -308,32 +312,11 @@
The Apache Wicket PMC is proud to announce Apache Wicket 6.9.0! This release marks the ninth minor release of Wicket 6. Starting with Wicket 6...
<a href='/2013/06/27/wicket-6.9.0-released.html'>more</a></li>
-
-<li>
- <a href='/2013/05/17/wicket-6.8.0-released.html'>Apache Wicket 6.8.0 released</a> - <span>17 May 2013</span><br />
- The Apache Wicket PMC is proud to announce Apache Wicket 6.8.0! This release marks the eighth minor release of Wicket 6. Starting with Wicket 6...
- <a href='/2013/05/17/wicket-6.8.0-released.html'>more</a></li>
-
</ul>
-<h1 id="books_about_wicket">Books about Wicket</h1>
+<h1 id='books_about_wicket'>Books about Wicket</h1>
<p>The following books are published regarding Apache Wicket (click a cover to learn more about the book):</p>
-
-<p><a href='/learn/books/awc.html'><img height='200px' src='/learn/books/awc.png' /></a></p>
-
-<p><a href='/learn/books/wia.html'><img height='200px' src='/learn/books/wia.png' /></a></p>
-
-<p><a href='/learn/books/ewdww.html'><img height='200px' src='/learn/books/ewdww.png' /></a></p>
-
-<p><a href='/learn/books/prowicket.html'><img height='200px' src='/learn/books/prowicket.png' /></a></p>
-
-<p><a href='/learn/books/kwij.html'><img height='200px' src='/learn/books/kwij.png' /></a></p>
-
-<p><a href='/learn/books/praxisbuchwicket.html'><img height='200px' src='/learn/books/praxisbuchwicket.png' /></a></p>
-
-<p><a href='/learn/books/wicket-jp.html'><img height='200px' src='/learn/books/wicket-jp.png' /></a></p>
-
-<p><a href='/learn/books/koda.html'><img height='200px' src='/learn/books/koda.jpg' /></a></p>
+<a href='/learn/books/awc.html'><img src='/learn/books/awc.png' height='200px' /></a><a href='/learn/books/wia.html'><img src='/learn/books/wia.png' height='200px' /></a><a href='/learn/books/ewdww.html'><img src='/learn/books/ewdww.png' height='200px' /></a><a href='/learn/books/prowicket.html'><img src='/learn/books/prowicket.png' height='200px' /></a><a href='/learn/books/kwij.html'><img src='/learn/books/kwij.png' height='200px' /></a><a href='/learn/books/praxisbuchwicket.html'><img src='/learn/books/praxisbuchwicket.png' height='200px' /></a><a href='/learn/books/wicket-jp.html'><img src='/learn/books/wicket-jp.png' height='200px' /></a><a href='/learn/books/koda.html'><img src='/learn/books/koda.jpg' height='200px' /></a>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/books/awc.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/books/awc.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/books/awc.html (original)
+++ wicket/common/site/trunk/_site/learn/books/awc.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,22 +174,22 @@
<div id="contentbody">
<h1>Books â Apache Wicket Cookbook</h1>
- <h2 id="description">Description</h2>
+ <h2 id='description'>Description</h2>
-<p>Apache Wicket is one of the most famous Java web application frameworks. Wicket simplifies web development and makes it fun. Are you bored of going through countless pages of theory to find out how to get your web development done? With this book in hand, you donât need to go through hundreds of pages to figure out how you will actually build a web application. You will get practical solutions to your common everyday development tasks to pace up your development activities.</p>
+<p>Apache Wicket is one of the most famous Java web application frameworks. Wicket simplifies web development and makes it fun. Are you bored of going through countless pages of theory to find out how to get your web development done? With this book in hand, you don’t need to go through hundreds of pages to figure out how you will actually build a web application. You will get practical solutions to your common everyday development tasks to pace up your development activities.</p>
-<p>Apache Wicket Cookbook provides you with information that gets your problems solved quickly without beating around the bush. This book is perfect for you if you are ready to take the next step from tutorials and step into the practical world. It will take you beyond the basics of using Apache Wicket and show you how to leverage Wicketâs advanced features to create simpler and more maintainable solutions to what at first may seem complex problems.</p>
+<p>Apache Wicket Cookbook provides you with information that gets your problems solved quickly without beating around the bush. This book is perfect for you if you are ready to take the next step from tutorials and step into the practical world. It will take you beyond the basics of using Apache Wicket and show you how to leverage Wicket’s advanced features to create simpler and more maintainable solutions to what at first may seem complex problems.</p>
<p>You will learn how to integrate with client-side technologies such as JavaScript libraries or Flash components, which will help you to build your application faster. You will discover how to use Wicket paradigms to factor out commonly used code into custom Components, which will reduce the maintenance cost of your application, and how to leverage the existing Wicket Components to make your own code simpler.</p>
<p>A straightforward Cookbook with highly focused practical recipes to make your web application development easier with the Wicket web framework</p>
-<h2 id="what_you_will_learn_from_this_book">What you will learn from this book</h2>
+<h2 id='what_you_will_learn_from_this_book'>What you will learn from this book</h2>
<ul>
<li>Leverage Wicket to implement a wide variety of both simple and advanced use cases in a narrative that gets straight to the point</li>
-<li>Make forms work in the crazy world of the Web by learning the ways of Wicketâs form processing</li>
+<li>Make forms work in the crazy world of the Web by learning the ways of Wicket’s form processing</li>
<li>Simplify localizing your Wicket applications</li>
@@ -197,30 +197,30 @@
<li>Leverage the built-in Table component to make displaying tabular data a snap</li>
-<li>Think Wicketâs Borders are not very useful? Learn to use them in unexpected places to simplify things</li>
+<li>Think Wicket’s Borders are not very useful? Learn to use them in unexpected places to simplify things</li>
<li>See how to integrate with Flash components and create interactive charts at the same time</li>
-<li>Web 1.0 too boring? Learn how to tame Wicketâs AJAX support and bring your application into Web 2.0</li>
+<li>Web 1.0 too boring? Learn how to tame Wicket’s AJAX support and bring your application into Web 2.0</li>
<li>Simplify your security code by learning various security techniques</li>
<li>An application cannot be built with Wicket alone; see how to make it play nice with other frameworks</li>
</ul>
-<h2 id="approach">Approach</h2>
+<h2 id='approach'>Approach</h2>
<p>This is a hands-on practical guide to a large variety of topics and use cases. This book tries to use real-world examples when possible, but is not afraid to come up with a contrived pretext if it makes explaining the problem simpler. Unlike a lot of other books, this one does not try to maintain a continuous theme from chapter to chapter, such as demonstrating solutions on the same fictional application; doing so would be almost impossible given the wide variety of recipes presented here. Instead, this book concentrates on focused problems users are likely to encounter and shows clear solutions in a step-by-step manner. This book tries to teach by example and is not afraid to show a lot of code because, after all, it is for coders.</p>
-<h2 id="who_this_book_is_written_for">Who this book is written for</h2>
+<h2 id='who_this_book_is_written_for'>Who this book is written for</h2>
<p>This book is for current users of the Apache Wicket framework; it is not an introduction to Wicket that will bore you with tons of theory. You are expected to have built or maintained a simple Wicket application in the past and to be looking to learn new and better ways of using Wicket. If you are ready to take your Wicket skills to the next level this book is for you.</p>
-<h2 id="about_the_author">About the author</h2>
+<h2 id='about_the_author'>About the author</h2>
-<p>Igor Vaynberg is a software architect with more than ten years of experience in the software field. His liking for computers was sparked when his parents got him a Sinclair Z80 when he was but ten years old. Since then he has worked with companies both large and small building modular and scalable web applications. Igorâs main interest is finding ways to simplify the development of complex user interfaces required by modern web applications. Igor is a committer for the Apache Wicket framework, the aim of which is to simplify the programming model as well as reintroduce OOP to the web UI tier. In his AFK time he enjoys snowboarding with his beautiful wife and playing with his amazing children.</p>
+<p>Igor Vaynberg is a software architect with more than ten years of experience in the software field. His liking for computers was sparked when his parents got him a Sinclair Z80 when he was but ten years old. Since then he has worked with companies both large and small building modular and scalable web applications. Igor’s main interest is finding ways to simplify the development of complex user interfaces required by modern web applications. Igor is a committer for the Apache Wicket framework, the aim of which is to simplify the programming model as well as reintroduce OOP to the web UI tier. In his AFK time he enjoys snowboarding with his beautiful wife and playing with his amazing children.</p>
-<h2 id="book_details">Book details</h2>
+<h2 id='book_details'>Book details</h2>
<table>
<tr>
<th>Title</th>
Modified: wicket/common/site/trunk/_site/learn/books/ewdww.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/books/ewdww.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/books/ewdww.html (original)
+++ wicket/common/site/trunk/_site/learn/books/ewdww.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -176,19 +176,19 @@
<h1>Books â Enjoying Web Development with Wicket</h1>
<p>Enjoying Web Development with Wicket is written by Kent Tong and is self published.</p>
-<h2 id="description">Description</h2>
+<h2 id='description'>Description</h2>
-<p>If youâd like to create AJAX web-based applications easily, then this book is for you. More importantly, it shows you how to do that with joy and feel good about your own work! You donât need to know servlet or JSP while your productivity will be much higher than using servlet or JSP directly. This is possible because weâre going to use a library called Wicket that makes complicated stuff simple and elegant.</p>
+<p>If you’d like to create AJAX web-based applications easily, then this book is for you. More importantly, it shows you how to do that with joy and feel good about your own work! You don’t need to know servlet or JSP while your productivity will be much higher than using servlet or JSP directly. This is possible because we’re going to use a library called Wicket that makes complicated stuff simple and elegant.</p>
-<p>How does it do that? First, it allows the web designer to work on the static contents and design of a page while allowing the developer to work on the dynamic contents of that page without stepping on each otherâs toes; Second, it allows developers to work with high level concepts such as objects and properties instead of HTTP URLs, query parameters or HTML string values; Third, it comes with powerful components such as calendar, tree and data grid and it allows you to create your own components for reuse in your own project.</p>
+<p>How does it do that? First, it allows the web designer to work on the static contents and design of a page while allowing the developer to work on the dynamic contents of that page without stepping on each other’s toes; Second, it allows developers to work with high level concepts such as objects and properties instead of HTTP URLs, query parameters or HTML string values; Third, it comes with powerful components such as calendar, tree and data grid and it allows you to create your own components for reuse in your own project.</p>
-<p>However, donât take our word for it! This book will quickly walk you through real world use cases to show you how to use Wicket and leave it up to you to judge.</p>
+<p>However, don’t take our word for it! This book will quickly walk you through real world use cases to show you how to use Wicket and leave it up to you to judge.</p>
-<h2 id="about_the_author">About the author</h2>
+<h2 id='about_the_author'>About the author</h2>
-<p>Kent Ka Iok Tong is the manager of the IT department of the Macau Productivity and Technology Transfer Center. With a Master degree in Computer Science from the New South Wales University, Sydney, Australia and having won the âMacao Programming Competition (Open Category)â in 1992, Mr. Tong has been involved in professional software development, training and project management since 1993. He is the author of several popular books on web technologies including Developing Web Services with Apache CXF and Axis2. He has also created an open source project âWicket Page Testâ for unit testing Wicket pages.</p>
+<p>Kent Ka Iok Tong is the manager of the IT department of the Macau Productivity and Technology Transfer Center. With a Master degree in Computer Science from the New South Wales University, Sydney, Australia and having won the “Macao Programming Competition (Open Category)” in 1992, Mr. Tong has been involved in professional software development, training and project management since 1993. He is the author of several popular books on web technologies including Developing Web Services with Apache CXF and Axis2. He has also created an open source project “Wicket Page Test” for unit testing Wicket pages.</p>
-<h2 id="book_details">Book details</h2>
+<h2 id='book_details'>Book details</h2>
<table>
<tr>
<th>Title</th>