Modified: wicket/common/site/trunk/_site/meet/vision.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/vision.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/meet/vision.html (original) +++ wicket/common/site/trunk/_site/meet/vision.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -184,7 +184,7 @@ <p>I once heard Josh Bloch talk about the power to weight ratio of an API. The highest compliment anyone could make of Wicket would be to suggest that Wicket has a lot of power and not much conceptual surface area.</p> -<p>In art, negative space is the part that’s not the subject. In music, negative space is the rest. In software, negative space is all the code that you managed to avoid writing. In all three disciplines, it’s what separates what is truly excellent from what is merely good.</p> +<p>In art, negative space is the part thatâs not the subject. In music, negative space is the rest. In software, negative space is all the code that you managed to avoid writing. In all three disciplines, itâs what separates what is truly excellent from what is merely good.</p> <p>Following this metaphor, if Wicket is our foreground object, it is defined in a negative sense by all the things that it is not (by the background).</p> @@ -192,13 +192,13 @@ <p>The more ways that Wicket can find to offload responsibilities (both now and in the future), the less it will be. And thus, the more it will be.</p> -<p>The difficulty moving forward with Wicket will be balancing all the day-to-day needs people are going to be bringing up with this overall vision of minimalism. There ultimately will be compromises, and the “trick” to making the right compromises is simply to agonize over all the options for a long time and then to only make the compromises that everyone agrees are really essential to what Wicket needs to be and do.</p> +<p>The difficulty moving forward with Wicket will be balancing all the day-to-day needs people are going to be bringing up with this overall vision of minimalism. There ultimately will be compromises, and the âtrickâ to making the right compromises is simply to agonize over all the options for a long time and then to only make the compromises that everyone agrees are really essential to what Wicket needs to be and do.</p> -<p>A big part of this process of agonizing is to act like doctors and “first, do no harm”. If some issue isn’t sitting well with everyone yet, there’s probably a reason for that. So, maybe the near-term solution is to simply do nothing and let people use the existing functionality until the limits to that approach (as well as competing ideas) are better understood.</p> +<p>A big part of this process of agonizing is to act like doctors and âfirst, do no harmâ. If some issue isnât sitting well with everyone yet, thereâs probably a reason for that. So, maybe the near-term solution is to simply do nothing and let people use the existing functionality until the limits to that approach (as well as competing ideas) are better understood.</p> -<p>It’s easy to add features. It’s often impossible to change or remove them.</p> +<p>Itâs easy to add features. Itâs often impossible to change or remove them.</p> -<p>Given this, the Wicket approach to the overall problem of evolving while keeping a high power to weight ratio will be partitioning off all controversial new ideas in a “wicket-stuff” package until they are broadly accepted. This way people can experiment and code away and check in lots of stuff without affecting the main codebase with untested ideas. Then, when ideas pan out to everyone’s satisfaction, the leads of the project will move them into the core.</p> +<p>Given this, the Wicket approach to the overall problem of evolving while keeping a high power to weight ratio will be partitioning off all controversial new ideas in a âwicket-stuffâ package until they are broadly accepted. This way people can experiment and code away and check in lots of stuff without affecting the main codebase with untested ideas. Then, when ideas pan out to everyoneâs satisfaction, the leads of the project will move them into the core.</p> </div> <div id="clearer"></div> <div id="footer"><span>
Modified: wicket/common/site/trunk/_site/start/download.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/download.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/start/download.html (original) +++ wicket/common/site/trunk/_site/start/download.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -174,29 +174,29 @@ <div id="contentbody"> <h1>Download Wicket releases</h1> - <p>Apache Wicket 6.14.0 is the current stable release. Most users get Apache Wicket using <a href='#maven'>Apache Maven’s dependency management</a>, which incidentally is the most convenient way of obtaining the latest and greatest Wicket.</p> + <p>Apache Wicket 6.14.0 is the current stable release. Most users get Apache Wicket using <a href="#maven">Apache Mavenâs dependency management</a>, which incidentally is the most convenient way of obtaining the latest and greatest Wicket.</p> -<h2 id='download'>Download</h2> +<h2 id="download">Download</h2> -<p>New projects should use <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.14.0'>Wicket 6.14.0</a> as their base.</p> +<p>New projects should use <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14.0</a> as their base.</p> <ul> -<li><strong>Latest stable release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.14.0'>6.14.0</a></li> +<li><strong>Latest stable release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>6.14.0</a></li> -<li><strong>Latest 6.x release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.14.0'>6.14.0</a></li> +<li><strong>Latest 6.x release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>6.14.0</a></li> -<li><strong>Latest 1.5.x release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/1.5.11'>1.5.11</a></li> +<li><strong>Latest 1.5.x release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>1.5.11</a></li> -<li><strong>Latest 1.4.x release</strong> (security updates only): <a href='http://www.apache.org/dyn/closer.cgi/wicket/1.4.23'>1.4.23</a></li> +<li><strong>Latest 1.4.x release</strong> (security updates only): <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.4.23";>1.4.23</a></li> -<li><strong>Archived releases</strong>: <a href='http://archive.apache.org/dist/wicket'>http://archive.apache.org/dist/wicket</a></li> +<li><strong>Archived releases</strong>: <a href="http://archive.apache.org/dist/wicket";>http://archive.apache.org/dist/wicket</a></li> </ul> -<p>We recommend you <a href='quickstart.html'>start</a> with our latest stable release.</p> +<p>We recommend you <a href="quickstart.html">start</a> with our latest stable release.</p> -<h3 id='requirements'>Requirements</h3> +<h3 id="requirements">Requirements</h3> -<h4 id='java_version'>Java version</h4> +<h4 id="java_version">Java version</h4> <ul> <li>Apache Wicket 6.x requires JDK 6.0 or newer</li> @@ -206,33 +206,33 @@ <li>Apache Wicket 1.4.x requires JDK 1.5 or newer</li> </ul> -<h4 id='mixing_wicket_versions'>Mixing Wicket versions</h4> +<h4 id="mixing_wicket_versions">Mixing Wicket versions</h4> <p>You cannot mix different Wicket versions in your project. You should always use the artifacts from a particular release train.</p> <p>For example it is <strong>NOT</strong> possible to use Wicket Extensions 1.5 in a Wicket 6 project. The same goes for 3rd party libraries: make sure you always use a compatible version of your 3rd party library.</p> -<h4 id='logging'>Logging</h4> +<h4 id="logging">Logging</h4> -<p>You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use <a href='http://logging.apache.org/log4j'>log4j</a>.</p> +<p>You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use <a href="http://logging.apache.org/log4j";>log4j</a>.</p> -<p>If you do, just include <strong>slf4j-log4j12.jar</strong> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href='http://www.slf4j.org/faq.html'>SLF4J site</a> for more information.</p> +<p>If you do, just include <strong>slf4j-log4j12.jar</strong> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href="http://www.slf4j.org/faq.html";>SLF4J site</a> for more information.</p> -<h2 id='migrating_from_earlier_versions'>Migrating from earlier versions</h2> +<h2 id="migrating_from_earlier_versions">Migrating from earlier versions</h2> <p>If you are migrating an existing application from earlier versions of Wicket you may find our migration guides invaluable:</p> <ul> -<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.3'>Wicket 1.2 to Wicket 1.3</a></li> +<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.3";>Wicket 1.2 to Wicket 1.3</a></li> -<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.4'>Wicket 1.3 to Wicket 1.4</a></li> +<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.4";>Wicket 1.3 to Wicket 1.4</a></li> -<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5'>Wicket 1.4 to Wicket 1.5</a></li> +<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5";>Wicket 1.4 to Wicket 1.5</a></li> -<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0'>Wicket 1.5 to Wicket 6</a></li> +<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0";>Wicket 1.5 to Wicket 6</a></li> </ul> -<h2 id='maven'>Maven</h2> +<h2 id="maven">Maven</h2> <p>Add the following snippet to your Maven project descriptor (<code>pom.xml</code>):</p> <div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span> @@ -240,17 +240,15 @@ <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'></dependency></span> -</code></pre> -</div> +</code></pre></div> <p>For the SLF4J log4j binding:</p> <div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span> <span class='nt'><groupId></span>org.slf4j<span class='nt'></groupId></span> <span class='nt'><artifactId></span>slf4j-log4j12<span class='nt'></artifactId></span> <span class='nt'><version></span>1.6.4<span class='nt'></version></span> <span class='nt'></dependency></span> -</code></pre> -</div> -<h2 id='snapshots_and_latest_bleedingedge_code'>SNAPSHOTs and latest bleeding-edge code</h2> +</code></pre></div> +<h2 id="snapshots_and_latest_bleedingedge_code">SNAPSHOTs and latest bleeding-edge code</h2> <p>If you wish to build the latest code from scratch, master and branches live in the Git repository: https://git-wip-us.apache.org/repos/asf/wicket.git</p> @@ -270,7 +268,7 @@ <li><strong>1.2.x</strong>: wicket-1.2.x</li> </ul> -<p>There’s also a Maven 2 repository providing SNAPSHOTs available here:</p> +<p>Thereâs also a Maven 2 repository providing SNAPSHOTs available here:</p> <div class='highlight'><pre><code class='xml'><span class='nt'><repositories></span> <span class='nt'><repository></span> <span class='nt'><releases></span> @@ -285,8 +283,7 @@ <span class='nt'><layout></span>default<span class='nt'></layout></span> <span class='nt'></repository></span> <span class='nt'></repositories></span> -</code></pre> -</div> +</code></pre></div> </div> <div id="clearer"></div> <div id="footer"><span> Modified: wicket/common/site/trunk/_site/start/index.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/index.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/start/index.html (original) +++ wicket/common/site/trunk/_site/start/index.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -175,9 +175,9 @@ <div id="contentbody"> <h1>Get Started</h1> <ul> -<li>Start with Apache Wicket using the <a href='quickstart.html'>quickstart</a></li> +<li>Start with Apache Wicket using the <a href="quickstart.html">quickstart</a></li> -<li><a href='download.html'>Download</a> the latest and greatest Wicket release</li> +<li><a href="download.html">Download</a> the latest and greatest Wicket release</li> <li>Or use one of the available third party <a href='http://www.jweekend.com/dev/LegUp' rel='nofollow'>Maven archetypes</a></li> </ul> Modified: wicket/common/site/trunk/_site/start/installing.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/installing.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/start/installing.html (original) +++ wicket/common/site/trunk/_site/start/installing.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -182,11 +182,11 @@ <li>logging</li> </ul> -<h2 id='required_dependencies_to_use_wicket'>Required dependencies to use Wicket</h2> +<h2 id="required_dependencies_to_use_wicket">Required dependencies to use Wicket</h2> -<p>While we are adamant users of Apache Maven and its build infrastructure, this may not be to everyone’s liking. However, if you wish to learn all about which dependencies you need for your Wicket project, we ask you to learn to read the POM file format and retrieve the required versions stated there. We take great care to keep the POM files up to date with the latest and greatest of each dependency.</p> +<p>While we are adamant users of Apache Maven and its build infrastructure, this may not be to everyoneâs liking. However, if you wish to learn all about which dependencies you need for your Wicket project, we ask you to learn to read the POM file format and retrieve the required versions stated there. We take great care to keep the POM files up to date with the latest and greatest of each dependency.</p> -<h3 id='compilation__testing'>Compilation & Testing</h3> +<h3 id="compilation__testing">Compilation & Testing</h3> <p>At a minimum a vanilla Wicket application requires for compilation:</p> @@ -202,7 +202,7 @@ <li>junit if you build Wicket from source or want to use <code>WicketTester</code> to test your pages and components</li> </ul> -<h3 id='runtime_dependencies'>Runtime dependencies</h3> +<h3 id="runtime_dependencies">Runtime dependencies</h3> <p>At a minimum a barebones Wicket application requires the following at runtime:</p> @@ -214,11 +214,11 @@ <li>slf4j-api and your slf4j implementation and required logging provider dependencies.</li> </ul> -<h2 id='logging'>Logging</h2> +<h2 id="logging">Logging</h2> -<p>As of Wicket 1.3.0, Wicket uses the <a href='http://www.slf4j.org/'>SLF4J</a> project for logging. SLF4J is similar to <a href='http://jakarta.apache.org/commons/logging/'>commons-logging</a>, in that it allows libraries/frameworks like Wicket to avoid forcing a choice of logging framework on their users.</p> +<p>As of Wicket 1.3.0, Wicket uses the <a href="http://www.slf4j.org/";>SLF4J</a> project for logging. SLF4J is similar to <a href="http://jakarta.apache.org/commons/logging/";>commons-logging</a>, in that it allows libraries/frameworks like Wicket to avoid forcing a choice of logging framework on their users.</p> -<p><strong>You cannot use Wicket without adding an SLF4J logging implementation to your classpath</strong>. Most people use <a href='http://logging.apache.org/log4j'>log4j</a>. If you do, just include <code>slf4j-log4j12.jar</code> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href='http://www.slf4j.org/faq.html'>SLF4J site</a> for more information.</p> +<p><strong>You cannot use Wicket without adding an SLF4J logging implementation to your classpath</strong>. Most people use <a href="http://logging.apache.org/log4j";>log4j</a>. If you do, just include <code>slf4j-log4j12.jar</code> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href="http://www.slf4j.org/faq.html";>SLF4J site</a> for more information.</p> </div> <div id="clearer"></div> <div id="footer"><span> Modified: wicket/common/site/trunk/_site/start/quickstart.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/quickstart.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/start/quickstart.html (original) +++ wicket/common/site/trunk/_site/start/quickstart.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -174,13 +174,13 @@ <div id="contentbody"> <h1>Create a Wicket Quickstart</h1> - <p>There are two really good reasons to create a Wicket quickstart. The first is if you just want to get started using Wicket quickly. The quickstart will set up a ready-to-use project in under a minute (depending on your bandwidth). Another great reason to create a quickstart is to accompany a bug report. If you report a bug in JIRA or on the mailing list, the core developers may not be able to recreate it easily. In most cases, you’ll be told “please create a quickstart and attach it to a JIRA issue”. If you don’t know how to do that, don’t worry - just follow the instructions below. (If you are submitting a quickstart for an issue report, please be sure to read the subheading below - “Submitting a quickstart for an issue report”</p> + <p>There are two really good reasons to create a Wicket quickstart. The first is if you just want to get started using Wicket quickly. The quickstart will set up a ready-to-use project in under a minute (depending on your bandwidth). Another great reason to create a quickstart is to accompany a bug report. If you report a bug in JIRA or on the mailing list, the core developers may not be able to recreate it easily. In most cases, youâll be told âplease create a quickstart and attach it to a JIRA issueâ. If you donât know how to do that, donât worry - just follow the instructions below. (If you are submitting a quickstart for an issue report, please be sure to read the subheading below - âSubmitting a quickstart for an issue reportâ</p> -<p>Quickstarts are made from a Maven archetype. So, you will need to have <a href='http://maven.apache.org'>Maven 2</a> installed and working (from the command line) before following this.</p> +<p>Quickstarts are made from a Maven archetype. So, you will need to have <a href="http://maven.apache.org";>Maven 2</a> installed and working (from the command line) before following this.</p> <p>Creating a quickstart provides only a very basic starting point for your Wicket project. If you are looking for examples of how to use Wicket and its various features, please refer to the <em>wicket-example</em> projects instead!</p> -<h2 id='creating_the_project__with_maven'>Creating the project - with Maven</h2> +<h2 id="creating_the_project__with_maven">Creating the project - with Maven</h2> <p>To create your project, copy and paste the command line generated after typing in the groupId, artifactId and version.</p> <style> @@ -262,7 +262,7 @@ </div> <br /> </div> -<h3 id='results'>Results</h3> +<h3 id="results">Results</h3> <p>This will produce the following project structure/files:</p> <div style='margin-left: 3em; border: 1px solid black'> @@ -293,53 +293,53 @@ Start.java </pre> </div> -<h3 id='using_maven_quickstart_with_a_specific_ide'>Using Maven quickstart with a specific IDE</h3> +<h3 id="using_maven_quickstart_with_a_specific_ide">Using Maven quickstart with a specific IDE</h3> <p>Maven has an integration with many IDEs. If you want to use your new Maven-based Wicket quickstart with your favorite IDE, see one of these instructions:</p> -<h4 id='eclipse'>Eclipse</h4> +<h4 id="eclipse">Eclipse</h4> <p>Change directory into the project that you just created. Now, run <code>mvn eclipse:eclipse</code>. This will set up the .project, .settings, and .classpath files that Eclipse requires.</p> -<p>Note that your workspace will have to have the classpath variable M2_REPO set to point to the directory where your local Maven repository exists. You can see this page for how to do that with Eclipse: <a href='http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html'>http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html</a></p> +<p>Note that your workspace will have to have the classpath variable M2_REPO set to point to the directory where your local Maven repository exists. You can see this page for how to do that with Eclipse: <a href="http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html";>http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html</a></p> -<p>Now, in Eclipse, you can choose “File” (menu), then “Import”, then “Existing project”. Navigate to the folder where your project exists and let Eclipse import it. The classpath should be fully configured.</p> +<p>Now, in Eclipse, you can choose âFileâ (menu), then âImportâ, then âExisting projectâ. Navigate to the folder where your project exists and let Eclipse import it. The classpath should be fully configured.</p> -<p>Alternatively install the <a href='http://m2eclipse.codehaus.org/'>m2eclipse</a> or <a href='http://www.eclipse.org/iam/'>Eclipse IAM</a> plugin and add the project directly.</p> +<p>Alternatively install the <a href="http://m2eclipse.codehaus.org/";>m2eclipse</a> or <a href="http://www.eclipse.org/iam/";>Eclipse IAM</a> plugin and add the project directly.</p> -<h4 id='idea'>IDEA</h4> +<h4 id="idea">IDEA</h4> -<p>From within IDEA, just use “File/Import Project”, choose the project directory and specify that this is a Maven project.</p> +<p>From within IDEA, just use âFile/Import Projectâ, choose the project directory and specify that this is a Maven project.</p> -<h4 id='netbeans'>NetBeans</h4> +<h4 id="netbeans">NetBeans</h4> <p>To create a NetBeans project, just open the pom.xml directly.</p> -<h3 id='more_examples'>More examples</h3> +<h3 id="more_examples">More examples</h3> -<p>Many more information and examples can be found on our Wiki or <a href='http://www.ralfebert.de/blog/wicket/wicket_eclipse_setup/'>here</a></p> +<p>Many more information and examples can be found on our Wiki or <a href="http://www.ralfebert.de/blog/wicket/wicket_eclipse_setup/";>here</a></p> -<h2 id='using_your_new_project'>Using your new project</h2> +<h2 id="using_your_new_project">Using your new project</h2> -<p>Wicket quickstart projects include a file named Start.java. If you open this file in your IDE (after configuring the project in your IDE), you can run it as a Java application. It will run an embedded Jetty instance that will run your app on <a href='http://localhost:8080'>http://localhost:8080</a> Navigate your browser to that address to see your app running.</p> +<p>Wicket quickstart projects include a file named Start.java. If you open this file in your IDE (after configuring the project in your IDE), you can run it as a Java application. It will run an embedded Jetty instance that will run your app on <a href="http://localhost:8080";>http://localhost:8080</a> Navigate your browser to that address to see your app running.</p> -<h3 id='using_the_jetty_plugin'>Using the Jetty Plugin</h3> +<h3 id="using_the_jetty_plugin">Using the Jetty Plugin</h3> -<p>The Jetty plugin is also enabled by default in the quickstart. If you are using Maven, you can change directory into the project and run the “mvn jetty:run” command. This will compile the project and deploy it to an embeded instance of the Jetty servlet engine, which will run on port 8080, by default. As a result, once running, your application will be available at <a href='http://localhost:8080'>http://localhost:8080</a>.</p> +<p>The Jetty plugin is also enabled by default in the quickstart. If you are using Maven, you can change directory into the project and run the âmvn jetty:runâ command. This will compile the project and deploy it to an embeded instance of the Jetty servlet engine, which will run on port 8080, by default. As a result, once running, your application will be available at <a href="http://localhost:8080";>http://localhost:8080</a>.</p> -<p>See the <a href='http://www.mortbay.org/maven-plugin/index.html'>Jetty plugin</a> documentation for configuration options, etc.</p> +<p>See the <a href="http://www.mortbay.org/maven-plugin/index.html";>Jetty plugin</a> documentation for configuration options, etc.</p> -<h2 id='submitting_a_quickstart_for_an_issue_report'>Submitting a quickstart for an issue report</h2> +<h2 id="submitting_a_quickstart_for_an_issue_report">Submitting a quickstart for an issue report</h2> -<h3 id='reproduce_the_problem'>Reproduce the problem</h3> +<h3 id="reproduce_the_problem">Reproduce the problem</h3> -<p>Assuming you have followed the instructions above, the quickstart is now created and ready for you to develop. Now comes the “duplicate the problem” part. Try to create pages or components that reproduce the problem you were trying to report. You can run the Start.java class from your IDE and go to <a href='http://localhost:8080'>http://localhost:8080</a> to see your test application. If you run the Start.java class in your IDE’s debug mode, you should be able to attach breakpoints and have automatic class and markup reloading.</p> +<p>Assuming you have followed the instructions above, the quickstart is now created and ready for you to develop. Now comes the âduplicate the problemâ part. Try to create pages or components that reproduce the problem you were trying to report. You can run the Start.java class from your IDE and go to <a href="http://localhost:8080";>http://localhost:8080</a> to see your test application. If you run the Start.java class in your IDEâs debug mode, you should be able to attach breakpoints and have automatic class and markup reloading.</p> -<p>If you can’t reproduce the problem - start looking at your own code. Keep adding pieces from your code until either you reproduce the problem, or else you’ve found the bug in your own code. A lot of times, you will find the bug in your code just by trying to create a quickstart that demonstrates the bug in ours.</p> +<p>If you canât reproduce the problem - start looking at your own code. Keep adding pieces from your code until either you reproduce the problem, or else youâve found the bug in your own code. A lot of times, you will find the bug in your code just by trying to create a quickstart that demonstrates the bug in ours.</p> -<h3 id='clean_up_the_quickstart_and_submit_it'>Clean up the quickstart and submit it</h3> +<h3 id="clean_up_the_quickstart_and_submit_it">Clean up the quickstart and submit it</h3> -<p>Once you have reproduced the desired behavior in your quickstart, it would be best to make it as small as possible before submitting. The best way to do this is to run the “mvn clean” command from the project directory. Then zip (or tar and gzip) the whole directory up and submit the zip (or tgz) file. (The mvn clean command removes all of the compiled classes and generated artifacts, generally in your “target” directory, leaving only the actual source.)</p> +<p>Once you have reproduced the desired behavior in your quickstart, it would be best to make it as small as possible before submitting. The best way to do this is to run the âmvn cleanâ command from the project directory. Then zip (or tar and gzip) the whole directory up and submit the zip (or tgz) file. (The mvn clean command removes all of the compiled classes and generated artifacts, generally in your âtargetâ directory, leaving only the actual source.)</p> </div> <div id="clearer"></div> <div id="footer"><span> Modified: wicket/common/site/trunk/_site/start/userguide.html URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/userguide.html?rev=1571985&r1=1571984&r2=1571985&view=diff ============================================================================== --- wicket/common/site/trunk/_site/start/userguide.html (original) +++ wicket/common/site/trunk/_site/start/userguide.html Wed Feb 26 10:10:32 2014 @@ -92,7 +92,7 @@ </h5> <ul> <li> - <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.13</a> + <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0";>Wicket 6.14</a> </li> <li> <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11";>Wicket 1.5</a> @@ -177,14 +177,14 @@ <p>The user guide has been written using the doc engine from Grails project and is available in the following formats:</p> <ul> -<li><a href='/guide/guide/index.html'>HTML</a></li> +<li><a href="/guide/guide/index.html">HTML</a></li> -<li><a href='/guide/guide/single.html'>HTML (single page)</a></li> +<li><a href="/guide/guide/single.html">HTML (single page)</a></li> -<li><a href='/guide/guide/single.pdf'>PDF</a></li> +<li><a href="/guide/guide/single.pdf">PDF</a></li> </ul> -<p>For more details about the format used to write the guide and to know how to contrinute, see <a href='/guide/guide/contributing.html'>the relative chapter</a>.</p> +<p>For more details about the format used to write the guide and to know how to contrinute, see <a href="/guide/guide/contributing.html">the relative chapter</a>.</p> </div> <div id="clearer"></div> <div id="footer"><span>
