Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's best to use the dependencyManagement tag in your parent pom to define your dependencies and their versions then reference these dependencies in your sub modules where needed. When you require other sub modules in your project (ie your common submodule from another submodule) then the dependencies will be found transitively. For example:</p> <p>In your parent pom:</p> <pre><code>&lt;dependencyManagement&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;junit&lt;/groupId&gt; &lt;artifactId&gt;junit&lt;/artifactId&gt; &lt;version&gt;4.7&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/dependencyManagement&gt; </code></pre> <p>In your common pom (notice there is no version or scope):</p> <pre><code>&lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;junit&lt;/groupId&gt; &lt;artifactId&gt;junit&lt;/artifactId&gt; &lt;/dependency&gt; &lt;/dependencies&gt; </code></pre> <p>And then you can just reference your common submodule from other submodules are you are already.</p>
    singulars
    1. This table or related slice is empty.
    1. POMaven multi-module: aggregate common dependencies in a single one?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrei Petrenko
    1. USCaps
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMaven multi-module: aggregate common dependencies in a single one?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBe aware that dependency management is viral, though. I.e. if A -> B, A -> C:1.0, and B -> C:2.0 by way of dependency management, then in building A, you'll get C:2.0 instead of C:1.0, as you would expect from typical transitive dependency rules. To get the version you want, A must use dependency management to force it to C:1.0. Hence: viral.
      singulars
      1. PO
      1. USRyan Stewart
    2. COYes, I know the dependencyManagement tag, but I see it more as a mean of enforcing dependencies versions across a project, without error-prone redundancy. However, you still need to declare the dependencies themselves in each module. I was rather thinking of a situation where **all** (or nearly) modules share some dependency: regardless of versioning, is it a better practice to define those _global_ dependencies in the parent (like I currently do) or create a module for that specific purpose, on which all other ones depend?
      singulars
      1. PO
      1. USEleaar
    3. COI use dependencyManagagement as described above and put each module's dependencies within the module level POM unless the dependency is for 100% of the modules always...then I put it in the parent POM. Do NOT put a dependency in the parent POM that is not needed in every child POM and definitely do not create a project just to pull in dependencies. It is not a big deal to repeat these dependencies across child modules because you do not need to supply the version as the dependencyManagement stanza in the parent does that for you.
      singulars
      1. PO
      1. USHDave
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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