X-Git-Url: https://juplo.de/gitweb/?p=website;a=blobdiff_plain;f=dist%2Fblog%2Farticle.html;h=43eed2f5ddb355e66ca04d09a8ce7cca284ec003;hp=1115bdd91da4bc13bd1224cd01f332e3ecc79561;hb=f837933de1896d90bfeb82500b10f403e6740a57;hpb=14646bdae51a709c3850573d89e404939bd88808 diff --git a/dist/blog/article.html b/dist/blog/article.html index 1115bdd9..43eed2f5 100644 --- a/dist/blog/article.html +++ b/dist/blog/article.html @@ -2,35 +2,20 @@ juplo - blog - Combining jetty-maven-plugin and wro4j-maven-plugin for Dynamic Reloading of LESS-Resources - - + + + + -
    -
  1. Home
  2. -
  3. Blog
  4. -
-
@@ -44,14 +29,14 @@

You cannot do both, use the Client-side mode of LESS to ease development and use the lesscss-maven-plugin 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 – which is best for development – and the pre-compiled mode – which is best for production. For the client-side mode you need something like:

   
-  <link rel="stylesheet" type="text/css" href="styles.less" />
+  <link rel="stylesheet/less" type="text/css" href="styles.less" />
   <script src="less.js" type="text/javascript"></script>
   
           

While, for the pre-compiled mode, you want to link to your stylesheets as usual, with:

   
-  <link rel="stylesheet" type="text/css" href="styles.css" />
+  <link rel="stylesheet/less" type="text/css" href="styles.css" />
   
           

While looking for a solution to this dilemma, I stumbled accross wro4j. 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.