Is a Maven multi-module project appropriate for independent programs?
<p>I've just started working on a project that has a lot of similarities in the code base between different programs. For example, four of the programs are parsing HTML pages, and each one has a util package with a Parser class (all of which are the same). My thought was to combine all these independent programs, in a structure like this:</p>

<pre><code>- util (util related classes)
    - src
    - pom.xml
- net (network related classes)
    - src
    - pom.xml
- app1
    - src
    - pom.xml
- app2
    - src
    - pom.xml
- app3
    - src
    - pom.xml
- pom.xml
</code></pre>

<p>Then, when I need to use Redis in any of the apps, I just import net.Reis package (or import util.Parser to use the HTML parser). However, I'm quite new to things, and even after reading the multi-module guide <a href="http://books.sonatype.com/mvnex-book/reference/multimodule-web-spring-sect-intro.html" rel="nofollow">here</a>, I am still unsure if this is an appropriate model for completely different (but in many ways related) programs.</p>