HTML-Vorlagen für Blog-Seiten und Formular-Beispiele
[website] / src / main / webapp / WEB-INF / views / blog / article.html
diff --git a/src/main/webapp/WEB-INF/views/blog/article.html b/src/main/webapp/WEB-INF/views/blog/article.html
new file mode 100644 (file)
index 0000000..f0edb2d
--- /dev/null
@@ -0,0 +1,419 @@
+<!DOCTYPE html>
+<html lang="en-US">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width" />
+    <title>Combining jetty-maven-plugin and wro4j-maven-plugin for Dynamic Reloading of LESS-Resources | juplo</title>
+    <link rel="profile" href="http://gmpg.org/xfn/11" />
+    <link rel="pingback" href="http://juplo.de/xmlrpc.php" />
+
+    <link rel="alternate" type="application/rss+xml" title="juplo &raquo; Feed" href="http://juplo.de/feed/" />
+<link rel="alternate" type="application/rss+xml" title="juplo &raquo; Comments Feed" href="http://juplo.de/comments/feed/" />
+
+            <script type="text/javascript">//<![CDATA[
+            // Google Analytics for WordPress by Yoast v4.3.3 | http://yoast.com/wordpress/google-analytics/
+            var _gaq = _gaq || [];
+            _gaq.push(['_setAccount', 'UA-571104-3']);
+                                           _gaq.push(['_trackPageview']);
+            (function () {
+                var ga = document.createElement('script');
+                ga.type = 'text/javascript';
+                ga.async = true;
+                ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+
+                var s = document.getElementsByTagName('script')[0];
+                s.parentNode.insertBefore(ga, s);
+            })();
+            //]]></script>
+                       <link rel="alternate" type="application/rss+xml" title="juplo &raquo; Combining jetty-maven-plugin and wro4j-maven-plugin for Dynamic Reloading of LESS-Resources Comments Feed" href="http://juplo.de/combining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources/feed/" />
+<link rel='stylesheet' id='admin-bar-css'  href='http://juplo.de/wp-includes/css/admin-bar.min.css?ver=3.6.1' type='text/css' media='all' />
+<link rel='stylesheet' id='style-css'  href='http://juplo.de/wp-content/themes/juplo-theme/style.css?ver=3.6.1' type='text/css' media='all' />
+<script type='text/javascript' src='http://juplo.de/wp-includes/js/comment-reply.min.js?ver=3.6.1'></script>
+<script type='text/javascript' src='http://juplo.de/wp-includes/js/jquery/jquery.js?ver=1.10.2'></script>
+<script type='text/javascript' src='http://juplo.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1'></script>
+<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://juplo.de/xmlrpc.php?rsd" />
+<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://juplo.de/wp-includes/wlwmanifest.xml" /> 
+<link rel='prev' title='hibernate4-maven-plugin 1.0.3 released!' href='http://juplo.de/hibernate4-maven-plugin-1-0-3-released/' />
+<meta name="generator" content="WordPress 3.6.1" />
+<link rel='canonical' href='http://juplo.de/combining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources/' />
+<link rel='shortlink' href='http://juplo.de/?p=140' />
+       <style type="text/css">.recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}</style>
+<style type="text/css" media="print">#wpadminbar { display:none; }</style>
+<style type="text/css" media="screen">
+       html { margin-top: 28px !important; }
+       * html body { margin-top: 28px !important; }
+</style>
+
+    <link rel="stylesheet" type="text/css" href="/css/base.css" />
+    <style type="text/css">
+      @import '/css/screen.css' screen and (min-width: 960px);
+      @import '/css/phone.css' screen and (max-width: 599px);
+      @import '/css/tiny.css' screen and (max-width: 399px);
+    </style>
+    <script src="/js/base.js"></script>
+    <!--[if IE 8]>
+      <script src="/js/ie8.js"></script>
+    <![endif]-->
+    <!--[if IE 7]>
+      <script src="/js/ie7.js"></script>
+    <![endif]-->
+    <!--[if lt IE 7]>
+      <script src="/js/ie6.js"></script>
+    <![endif]-->
+
+  </head>
+  <body class="single single-post postid-140 single-format-standard logged-in admin-bar no-customize-support" onload="prettyPrint()">
+    <div id="page">
+      <header id="header">
+        <a href="http://juplo.de/" title="juplo" rel="home" id="logo">juplo</a>
+        <span id="slogan">Java bits from nerds for nerds</span>
+        <hr class="h"/>
+      </header>
+    <div class="fc cols_2">
+      <div class="content cf">
+        <div id="content" class="main">
+           
+<article id="post-140" class="post-140 post type-post status-publish format-standard hentry category-jetty category-less category-maven category-wro4j">
+    <div class="entry-header">
+        <h1 class="entry-title">Combining jetty-maven-plugin and wro4j-maven-plugin for Dynamic Reloading of LESS-Resources</h1>
+        <div class="entry-meta">
+            Posted on <a href="http://juplo.de/combining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources/" title="12:58" rel="bookmark"><time class="entry-date" datetime="2013-12-06T12:58:17+00:00" pubdate>December 6, 2013</time></a><span class="byline"> by <span class="author vcard"><a class="url fn n" href="http://juplo.de/author/kai/" title="View all posts by Kai Moritz" rel="author">Kai Moritz</a></span></span>        </div><!-- .entry-meta -->
+    </div><!-- .entry-header -->
+    <div class="entry-content">
+        <p>Ever searched for a simple configuration, that lets you use your <a href="http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://wiki.eclipse.org']);" title="See the documentation for mor information">jetty-maven-plugin</a> as you are used to, while working with <a href="http://www.lesscss.org/" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://www.lesscss.org']);" title="See LESS CSS documentation for mor informations">LESS</a> to simplify your stylesheets?</p>
+<p>You cannot do both, use the <a href="http://www.lesscss.org/#usage" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://www.lesscss.org']);" title="More about the client-side usage of LESS">Client-side mode</a> of LESS to ease development and use the <a href="https://github.com/marceloverdijk/lesscss-maven-plugin" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://github.com']);" title="Homepage of the official LESS CSS maven plugin">lesscss-maven-plugin</a> to automatically compile the LESS-sources into CSS for production. That does not work, because your stylesheets must be linked in different ways if you are switching between the client-side mode &#8211; which is best for development &#8211; and the pre-compiled mode &#8211; which is best for production. For the client-side mode you need something like:</p>
+<pre class="prettyprint linenums">\r
+<code class="html">\r
+&lt;link rel="stylesheet/less" type="text/css" href="styles.less" /&gt;\r
+&lt;script src="less.js" type="text/javascript"&gt;&lt;/script&gt;\r
+</code>\r
+</pre>
+<p>While, for the pre-compiled mode, you want to link to your stylesheets as usual, with:</p>
+<pre class="prettyprint linenums">\r
+<code class="html">\r
+&lt;link rel="stylesheet" type="text/css" href="styles.css" /&gt;\r
+</code>\r
+</pre>
+<p>While looking for a solution to this dilemma, I stumbled accross <a href="https://code.google.com/p/wro4j/" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See the documentation of ths wounderfull tool">wro4j</a>. Originally intended, to speed up page-delivery by combining and minimizing multiple resources into one through the use of a servlet-filter, this tool also comes with a maven-plugin, that let you do the same offline, while compiling your webapp.</p>
+<p>The idea is, to use the <a href="http://code.google.com/p/wro4j/wiki/MavenPlugin" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See the documentation of hte wro4j-maven-plugin">wro4j-maven-plugin</a> to compile and combine your LESS-sources into CSS for production and to use the <a href="http://code.google.com/p/wro4j/wiki/Installation" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See how to configure the filter">wro4j filter</a>, to dynamically deliver the compiled CSS while developing. This way, you do not have to alter your HTML-code, when switching between development and production, because you always link to the CSS-files.</p>
+<p>So, lets get dirty!</p>
+<h2>Step 1: Configure wro4j</h2>
+<p>First, we configure <strong>wro4j</strong>, like as we want to use it to speed up our page. The details are explained and linked on wro4j&#8217;s <a href="http://code.google.com/p/wro4j/wiki/GettingStarted" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="Visit the Getting-Started-Page">Getting-Started-Page</a>. In short, we just need two files: <strong>wro.xml</strong> and <strong>wro.properties</strong>.</p>
+<h3>wro.xml</h3>
+<p>wro.xml tells wro4j, which resources should be combined and how the result should be named. I am using the following configuration to generate all LESS-Sources beneath <code>base/</code> into one CSS-file called <code>base.css</code>:</p>
+<pre class="prettyprint linenums">\r
+<code class="xml">\r
+&lt;groups xmlns="http://www.isdc.ro/wro"&gt;\r
+  &lt;group name="base"&gt;\r
+    &lt;css&gt;/less/base/*.less&lt;/css&gt;\r
+  &lt;/group&gt;\r
+</code>\r
+</pre>
+<p>wro4j looks for <code>/less/base/*.less</code> inside the root of the web-context, which is equal to <code>src/main/webapp</code> in a normal maven-project. There are <a href="http://code.google.com/p/wro4j/wiki/ResourceTypes" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See the resource locator documentation of wro4j for more details">other ways to specifie the resources</a>, which enable you to store them elswhere. But this approach works best for our goal, because the path is understandable for both: the wro4j servlet-filter, we are configuring now for our development-environment, and the wro4j-maven-plugin, that we will configure later for build-time compilation.</p>
+<h3>wro.properties</h3>
+<p>wro.properties in short tells wro4j, how or if it should convert the combined sources and how it should behave. I am using the following configuration to tell wro4j, that it should convert <code>*.less</code>-sources into CSS and do that on <em>every request</em>:</p>
+<pre class="prettyprint linenums">\r
+<code class="properties">\r
+preProcessors=less4j\r
+disableCache=true\r
+</code>\r
+</pre>
+<p>You can do a lot more here. There are countless <a href="http://code.google.com/p/wro4j/wiki/ConfigurationOptions" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See all configuration options">configuration options</a> to fine-tune the behaviour of wro4j. The <code>disableCache=true</code> is crucial, because we would not see the changes take effect when developing with <strong>jetty-maven-plugin</strong> later on. You can also do much more with your resources here, for example <a href="https://code.google.com/p/wro4j/wiki/AvailableProcessors" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See all available processors">minimizing</a>. But for our goal, we are now only intrested in the compilation of our LESS-sources.</p>
+<h2>Step 2: Configure the wro4j servlet-filter</h2>
+<p>Configuring the filter in the <strong>web.xml</strong> is easy. It is explained in wro4j&#8217;s <a href="https://code.google.com/p/wro4j/wiki/Installation" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="See the installation instructions for the wro4j servlet-filter">installation-insctuctions</a>. But the trick is, that we do not want to configure that filter for the production-version of our webapp, because we want to compile the resources offline, when the webapp is build. To acchieve this, we can use the <code>&lt;overrideDescriptor&gt;</code>-Parameter of the <a href="http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#Configuring_Your_WebApp" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://wiki.eclipse.org']);" title="Read more about the configuration of the jetty-maven-plugin">jetty-maven-plugin</a>.</p>
+<h2>&lt;overrideDescriptor&gt;</h2>
+<p>This parameter lets you specify additional configuration options for the web.xml of your webapp. I am using the following configuration for my jetty-maven-plugin:</p>
+<pre class="prettyprint linenums">\r
+<code class="xml">\r
+&lt;plugin&gt;\r
+  &lt;groupId&gt;org.eclipse.jetty&lt;/groupId&gt;\r
+  &lt;artifactId&gt;jetty-maven-plugin&lt;/artifactId&gt;\r
+  &lt;configuration&gt;\r
+    &lt;webApp&gt;\r
+      &lt;overrideDescriptor&gt;${project.basedir}/src/test/resources/jetty-web.xml&lt;/overrideDescriptor&gt;\r
+    &lt;/webApp&gt;\r
+  &lt;/configuration&gt;\r
+  &lt;dependencies&gt;\r
+    &lt;dependency&gt;\r
+      &lt;groupId&gt;ro.isdc.wro4j&lt;/groupId&gt;\r
+      &lt;artifactId&gt;wro4j-core&lt;/artifactId&gt;\r
+      &lt;version&gt;${wro4j.version}&lt;/version&gt;\r
+    &lt;/dependency&gt;\r
+    &lt;dependency&gt;\r
+      &lt;groupId&gt;ro.isdc.wro4j&lt;/groupId&gt;\r
+      &lt;artifactId&gt;wro4j-extensions&lt;/artifactId&gt;\r
+      &lt;version&gt;${wro4j.version}&lt;/version&gt;\r
+      &lt;exclusions&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;javax.servlet&lt;/groupId&gt;\r
+            &lt;artifactId&gt;servlet-api&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.apache.commons&lt;/groupId&gt;\r
+            &lt;artifactId&gt;commons-lang3&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;commons-io&lt;/groupId&gt;\r
+            &lt;artifactId&gt;commons-io&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;commons-pool&lt;/groupId&gt;\r
+            &lt;artifactId&gt;commons-pool&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.springframework&lt;/groupId&gt;\r
+            &lt;artifactId&gt;spring-web&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;com.google.code.gson&lt;/groupId&gt;\r
+            &lt;artifactId&gt;gson&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;com.google.javascript&lt;/groupId&gt;\r
+            &lt;artifactId&gt;closure-compiler&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;com.github.lltyk&lt;/groupId&gt;\r
+            &lt;artifactId&gt;dojo-shrinksafe&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.jruby&lt;/groupId&gt;\r
+            &lt;artifactId&gt;jruby-core&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+          &lt;groupId&gt;org.jruby&lt;/groupId&gt;\r
+          &lt;artifactId&gt;jruby-stdlib&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.jruby&lt;/groupId&gt;\r
+            &lt;artifactId&gt;jruby-stdlib&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;me.n4u.sass&lt;/groupId&gt;\r
+            &lt;artifactId&gt;sass-gems&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;nz.co.edmi&lt;/groupId&gt;\r
+            &lt;artifactId&gt;bourbon-gem-jar&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.codehaus.gmaven.runtime&lt;/groupId&gt;\r
+            &lt;artifactId&gt;gmaven-runtime-1.7&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;jshint&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;less&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;emberjs&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;handlebars&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;coffee-script&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;jslint&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;json2&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+        &lt;exclusion&gt;\r
+            &lt;groupId&gt;org.webjars&lt;/groupId&gt;\r
+            &lt;artifactId&gt;jquery&lt;/artifactId&gt;\r
+        &lt;/exclusion&gt;\r
+      &lt;/exclusions&gt;\r
+    &lt;/dependency&gt;\r
+  &lt;/dependencies&gt;\r
+&lt;/plugin&gt;</code>\r
+</pre>
+<p>The dependencies to <strong>wro4j-core</strong> and <strong>wro4j-extensions</strong> are needed by jetty, to be able to enable the filter defined below. Unfortunatly, one of the transitive dependencies of <code>wro4j-extensions</code> triggers an uggly error when running the jetty-maven-plugin. Therefore, all unneeded dependencies of <code>wro4j-extensions</code> are excluded, as a workaround for this error/bug.</p>
+<h2>jetty-web.xml</h2>
+<p>And my jetty-web.xml looks like this:</p>
+<pre class="prettyprint linenums">\r
+<code class="xml">\r
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;\r
+&lt;web-app xmlns="http://java.sun.com/xml/ns/javaee"\r
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\r
+  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"\r
+  version="2.5"&gt;\r
+  &lt;filter&gt;\r
+    &lt;filter-name&gt;wro&lt;/filter-name&gt;\r
+    &lt;filter-class&gt;ro.isdc.wro.http.WroFilter&lt;/filter-class&gt;\r
+  &lt;/filter&gt;\r
+  &lt;filter-mapping&gt;\r
+    &lt;filter-name&gt;wro&lt;/filter-name&gt;\r
+    &lt;url-pattern&gt;*.css&lt;/url-pattern&gt;\r
+  &lt;/filter-mapping&gt;\r
+&lt;/web-app&gt;\r
+</code>\r
+</pre>
+<p>The filter processes any URI&#8217;s that end with <code>.css</code>. This way, the wro4j servlet-filter makes <code>base.css</code> available under any path, because for exampl <code>/base.css</code>, <code>/css/base.css</code> and <code>/foo/bar/base.css</code> all end with <code>.css</code>.</p>
+<p>This is all, that is needed to develop with dynamically reloadable compiled LESS-resources. Just fire up your browser and browse to <code>/what/you/like/base.css</code>. (But do not forget to put some LESS-files in <code>src/main/webapp/less/base/</code> first!)</p>
+<h2>Step 3: Install wro4j-maven-plugin</h2>
+<p>All that is left over to configure now, is the build-process. If you would build and deploy your webapp now, the CSS-file <code>base.css</code> would not be generated and the link to your stylesheet, that already works in our jetty-maven-plugin environment would point to a 404. Hence, we need to set up the <strong>wro4j-maven-plugin</strong>. I am using this configuration:</p>
+<pre class="prettyprint linenums">\r
+<code class="xml">\r
+&lt;plugin&gt;\r
+  &lt;groupId&gt;ro.isdc.wro4j&lt;/groupId&gt;\r
+  &lt;artifactId&gt;wro4j-maven-plugin&lt;/artifactId&gt;\r
+  &lt;version&gt;${wro4j.version}&lt;/version&gt;\r
+  &lt;configuration&gt;\r
+    &lt;wroManagerFactory&gt;ro.isdc.wro.maven.plugin.manager.factory.ConfigurableWroManagerFactory&lt;/wroManagerFactory&gt;\r
+    &lt;cssDestinationFolder&gt;${project.build.directory}/${project.build.finalName}/css/&lt;/cssDestinationFolder&gt;\r
+  &lt;/configuration&gt;\r
+  &lt;executions&gt;\r
+    &lt;execution&gt;\r
+      &lt;phase&gt;package&lt;/phase&gt;\r
+      &lt;goals&gt;\r
+        &lt;goal&gt;run&lt;/goal&gt;\r
+      &lt;/goals&gt;\r
+    &lt;/execution&gt;\r
+  &lt;/executions&gt;\r
+&lt;/plugin&gt;\r
+</code>\r
+</pre>
+<p>I connected the <code>run</code>-goal with the <code>package</code>-phase, because the statically compiled CSS-file is needed only in the final war. The <code>ConfigurableWroManagerFactory</code> tells wro4j, that it should look up further configuration options in our <code>wro.properties</code>-file, where we tell wro4j, that it should compile our LESS-resources. The <code>&lt;cssDestinationFolder&gt;</code>-tag tells wro4j, where it should put the generated CSS-file. You can adjust that to suite your needs.</p>
+<p>That&#8217;s it: now the same CSS-file, which is created on the fly by the wro4j servlet-filter when using <code>mvn jetty:run</code> and, thus, enables dynamic reloading of our LESS-resources, is generated during the build-process by the wro4j-maven-plugin.</p>
+<h2>Cleanup and further considerations</h2>
+<h3>lesscss-maven-plugin</h3>
+<p>If you already compile your LESS-resources with the lesscss-maven-plugin, you can stick with it and skip step 3. But I strongly recommend giving wro4j-maven-plugin a try, because it is a much more powerfull tool, that can speed up your final webapp even more.</p>
+<h3>Clean up your mess </h3>
+<p>With a configuration like the above one, your LESS-resources and wro4j-configuration-files will be packed into your production-war. That might be confusing later, because neither wro4j nor LESS is used in the final war. You can add the following to your <code>pom.xml</code> to exclude these files from your war for the sake of clarity:</p>
+<pre class="prettyprint linenums">\r
+<code class="xml">\r
+&lt;plugin&gt;\r
+  &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;\r
+  &lt;configuration&gt;\r
+    &lt;warSourceExcludes&gt;\r
+      WEB-INF/wro.*,\r
+      less/**\r
+    &lt;/warSourceExcludes&gt;\r
+  &lt;/configuration&gt;\r
+&lt;/plugin&gt;\r
+</code>\r
+</pre>
+<h3>What&#8217;s next?</h3>
+<p>We only scrached the surface, of what can be done with wro4j. Based on this configuration, you can easily enable additional features to fine-tune your final build for maximum speed. You really should take a look at the <a href="https://code.google.com/p/wro4j/wiki/AvailableProcessors" onclick="javascript:_gaq.push(['_trackEvent','outbound-article','http://code.google.com']);" title="Available Processors">list of available Processors</a>!</p>
+            </div><!-- .entry-content -->
+    <footer class="entry-meta">
+        This entry was posted in <a href="http://juplo.de/category/jetty/" title="View all posts in Jetty" rel="category tag">Jetty</a>, <a href="http://juplo.de/category/less/" title="View all posts in less" rel="category tag">less</a>, <a href="http://juplo.de/category/maven/" title="View all posts in Maven" rel="category tag">Maven</a>, <a href="http://juplo.de/category/wro4j/" title="View all posts in wro4j" rel="category tag">wro4j</a>. Bookmark the <a href="http://juplo.de/combining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources/" title="Permalink to Combining jetty-maven-plugin and wro4j-maven-plugin for Dynamic Reloading of LESS-Resources" rel="bookmark">permalink</a>. 
+    </footer><!-- .entry-meta -->
+</article><!-- #post-140 -->
+
+<!-- You can start editing here. -->
+
+
+                       <!-- If comments are open, but there are no comments. -->
+
+        
+
+<div id="respond">
+
+<h3>Leave a Reply</h3>
+
+<div id="cancel-comment-reply">
+       <small><a rel="nofollow" id="cancel-comment-reply-link" href="/combining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources/#respond" style="display:none;">Click here to cancel reply.</a></small>
+</div>
+
+
+<form action="http://juplo.de/wp-comments-post.php" method="post" id="commentform">
+
+
+<p>Logged in as <a href="http://juplo.de/wp-admin/profile.php">Kai Moritz</a>. <a href="http://juplo.de/wp-login.php?action=logout&amp;redirect_to=http%3A%2F%2Fjuplo.de%2Fcombining-jetty-maven-plugin-and-wro4j-maven-plugin-for-dynamic-reloading-of-less-resources%2F&amp;_wpnonce=09e5cb501d" title="Log out of this account">Log out &raquo;</a></p>
+
+
+<!--<p><small><strong>XHTML:</strong> You can use these tags: <code>&lt;a href=&quot;&quot; title=&quot;&quot;&gt; &lt;abbr title=&quot;&quot;&gt; &lt;acronym title=&quot;&quot;&gt; &lt;b&gt; &lt;blockquote cite=&quot;&quot;&gt; &lt;cite&gt; &lt;code&gt; &lt;del datetime=&quot;&quot;&gt; &lt;em&gt; &lt;i&gt; &lt;q cite=&quot;&quot;&gt; &lt;strike&gt; &lt;strong&gt; </code></small></p>-->
+
+<p><textarea name="comment" id="comment" cols="58" rows="10" tabindex="4"></textarea></p>
+
+<p><input name="submit" type="submit" id="submit" tabindex="5" value="Submit Comment" />
+<input type='hidden' name='comment_post_ID' value='140' id='comment_post_ID' />
+<input type='hidden' name='comment_parent' id='comment_parent' value='0' />
+</p>
+<input type="hidden" id="_wp_unfiltered_html_comment_disabled" name="_wp_unfiltered_html_comment_disabled" value="2096655c89" /><script>(function(){if(window===window.parent){document.getElementById('_wp_unfiltered_html_comment_disabled').name='_wp_unfiltered_html_comment';}})();</script>
+<p style="display: none;"><input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="f31e001227" /></p>
+</form>
+
+</div>
+
+        </div>
+              <div class="marginal">
+        <nav id="nav">
+          <hr />
+          <a id="navigation"></a>
+        </nav>
+        <div id="secondary" class="widget-area" role="complementary">
+                                <aside id="archives" class="widget">
+              <h1 class="widget-title">Archives</h1>
+              <ul>
+                       <li><a href='http://juplo.de/2013/12/' title='December 2013'>December 2013</a></li>
+       <li><a href='http://juplo.de/2013/10/' title='October 2013'>October 2013</a></li>
+       <li><a href='http://juplo.de/2013/08/' title='August 2013'>August 2013</a></li>
+       <li><a href='http://juplo.de/2013/01/' title='January 2013'>January 2013</a></li>
+       <li><a href='http://juplo.de/2012/11/' title='November 2012'>November 2012</a></li>
+              </ul>
+            </aside>
+            <aside id="categories" class="widget">
+              <h1 class="widget-title">Most Used Categories</h1>
+              <ul>
+                       <li class="cat-item cat-item-4"><a href="http://juplo.de/category/java/" title="View all posts filed under Java">Java</a> (7)
+</li>
+       <li class="cat-item cat-item-8"><a href="http://juplo.de/category/maven/" title="View all posts filed under Maven">Maven</a> (7)
+</li>
+       <li class="cat-item cat-item-6"><a href="http://juplo.de/category/hibernate/" title="View all posts filed under Hibernate">Hibernate</a> (6)
+</li>
+       <li class="cat-item cat-item-9"><a href="http://juplo.de/category/jpa/" title="View all posts filed under JPA">JPA</a> (1)
+</li>
+       <li class="cat-item cat-item-10"><a href="http://juplo.de/category/appengine/" title="View all posts filed under appengine">appengine</a> (1)
+</li>
+       <li class="cat-item cat-item-11"><a href="http://juplo.de/category/oauth2/" title="View all posts filed under oauth2">oauth2</a> (1)
+</li>
+       <li class="cat-item cat-item-12"><a href="http://juplo.de/category/jetty/" title="View all posts filed under Jetty">Jetty</a> (1)
+</li>
+       <li class="cat-item cat-item-13"><a href="http://juplo.de/category/wro4j/" title="View all posts filed under wro4j">wro4j</a> (1)
+</li>
+       <li class="cat-item cat-item-14"><a href="http://juplo.de/category/less/" title="View all posts filed under less">less</a> (1)
+</li>
+              </ul>
+            </aside>
+            <aside id="search" class="widget widget_search">
+              <h1 class="widget-title">Search</h1>
+              <form role="search" method="get" id="searchform" class="searchform" action="http://juplo.de/">
+                               <div>
+                                       <label class="screen-reader-text" for="s">Search for:</label>
+                                       <input type="text" value="" name="s" id="s" />
+                                       <input type="submit" id="searchsubmit" value="Search" />
+                               </div>
+                       </form>            </aside>
+                  </div><!-- #secondary .widget-area -->
+        <div id="tertiary" class="widget-area" role="supplementary">
+                  </div><!-- #tertiary .widget-area -->
+
+      </div>
+      </div>
+    </div>
+          <footer id="footer">
+        <hr />
+        <ul id="footerlinks">
+          <li class="f" id="copyright">© <strong>mo</strong> 2013</li>
+        </ul>
+      </footer>
+    </div>
+  </body>
+</html>