Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Within your Development directory you would have a pom which would look something like the following:</p> <pre><code>&lt;project&gt; &lt;groupId&gt;yourGroup&lt;/groupId&gt; &lt;artifactId&gt;project&lt;/artifactId&gt; &lt;packaging&gt;pom&lt;/packaging&gt; &lt;modules&gt; &lt;module&gt;coreLibrary&lt;/module&gt; &lt;module&gt;swingApp&lt;/module&gt; &lt;module&gt;webServices&lt;/module&gt; &lt;/modules&gt; &lt;/project&gt; </code></pre> <p>yeah, I've left out some of the other elements, so fill in whatever else you need for a complete pom.</p> <p>Then, your coreLibrary, swingApp, and webServices modules would each have a pom with a parent element, and any dependencies, as follows</p> <pre><code>&lt;project&gt; &lt;parent&gt; &lt;groupId&gt;yourGroup&lt;/groupId&gt; &lt;artifactId&gt;project&lt;/artifactId&gt; &lt;version&gt;yourVersion&lt;/version&gt; &lt;/parent&gt; &lt;artifactId&gt;webServices&lt;/artifactId&gt; &lt;packaging&gt;war&lt;/packaging&gt; &lt;version&gt;yourVersion&lt;/version&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;yourGroup&lt;/groupId&gt; &lt;artifactId&gt;coreLibrary&lt;/artifactId&gt; &lt;version&gt;yourVersion&lt;/version&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/project&gt; </code></pre> <p>If you build at the root level, then it will build all 3 modules, or, even better, you could use the --also-make option to build only webServices and its dependencies (in this case coreLibrary)</p> <pre><code>mvn -am --projects webServices clean install </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload