<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maven on fournm</title>
    <link>https://4nm.us/tags/maven/</link>
    <description>Recent posts in Maven from fournm</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Mar 2017 00:38:37 -0700</lastBuildDate>
    <atom:link href="https://4nm.us/tags/maven/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>javascript and java in harmony</title>
      <link>https://4nm.us/posts/2017-javascript-and-java-in-harmony/</link>
      <pubDate>Tue, 14 Mar 2017 00:38:37 -0700</pubDate>
      <guid>https://4nm.us/posts/2017-javascript-and-java-in-harmony/</guid>
      
          
              <category>programming</category>
          
              <category>javascript</category>
          
              <category>java</category>
          
              <category>maven</category>
          
      
      <description>
        &lt;p&gt;Part three of the series on Maven, Java, and Javascript together, and I&amp;rsquo;m happy to say I&amp;rsquo;ve got good news.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s been more updates to the frontend plugin, so as of version 1.3 you can most certainly do everything that I originally set out.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Using node + webpack as part of a Maven build process instead of hideous combinations of wro and others&lt;/li&gt;&#xA;&lt;li&gt;Changes to JS and LESS files automatically recompile&lt;/li&gt;&#xA;&lt;li&gt;The compiled changes are picked up immediately by Spring for use&lt;/li&gt;&#xA;&lt;li&gt;Changing one file shouldn&amp;rsquo;t make everything a source of neverending delay and pain&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The answer here had a few components, not all of which I&amp;rsquo;m sure people will agree with, but here&amp;rsquo;s the breakdown.&lt;/p&gt;    
        
          <a href="https://4nm.us/posts/2017-javascript-and-java-in-harmony/">More ...</a>
        
      </description>
    </item>
    <item>
      <title>js and maven addendum</title>
      <link>https://4nm.us/posts/2017-js-and-maven-addendum/</link>
      <pubDate>Fri, 20 Jan 2017 23:24:18 -0800</pubDate>
      <guid>https://4nm.us/posts/2017-js-and-maven-addendum/</guid>
      
          
              <category>java</category>
          
              <category>maven</category>
          
              <category>programming</category>
          
              <category>javascript</category>
          
      
      <description>
        &lt;p&gt;Since writing up that post, I noticed there&amp;rsquo;s an update to &lt;code&gt;frontend-maven-plugin&lt;/code&gt; that contains a configuration setting to add an &lt;code&gt;outputdir&lt;/code&gt; that automatically refreshes the given folder inside of Eclipse. That&amp;rsquo;s wonderful, it&amp;rsquo;s exactly what I wanted.&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately, it doesn&amp;rsquo;t seem to force the rebuild of the webjar that project was building, which means I still have to manually refresh. Sigh. I&amp;rsquo;ll figure it out at some point, but until then, if you&amp;rsquo;re not supplying your assets using webjars it&amp;rsquo;ll work great.&lt;/p&gt;    
        
          <a href="https://4nm.us/posts/2017-js-and-maven-addendum/">More ...</a>
        
      </description>
    </item>
  </channel>
</rss>
