Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Original Answer: The <a href="http://m2eclipse.sonatype.org/" rel="nofollow">M2Eclipse</a> plugin, if you are not using it already, allows you to do this. Once installed, remove </p> <pre><code>&lt;systemPath&gt;${basedir}/../B/target/B-0.1.jar&lt;/systemPath&gt; </code></pre> <p>from A's pom.xml and make sure the groupid, artifactid, version match up with what is defined in B's pom.xml</p> <p>Then right-click on the project, Maven-> Enable Dependency Resolution. The build should now look at B's local project</p> <p>Edit:</p> <p>If B's pom.xml looks like this (from your example):</p> <pre><code>&lt;project xmlns="..." xmlns:xsi="..." xsi:schemaLocation="..."&gt; &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;groupId&gt;com.thetus&lt;/groupId&gt; &lt;artifactId&gt;irisMDK&lt;/artifactId&gt; &lt;packaging&gt;jar&lt;/packaging&gt; &lt;name&gt;irisMDK&lt;/name&gt; &lt;version&gt;0.1&lt;/version&gt; ... &lt;/project&gt; </code></pre> <p>In A's pom (which depends on Project B) your dependency should look like:</p> <pre><code>&lt;project&gt; ... &lt;dependencies&gt; &lt;!--Attributes of project that this project is dependent upon, as defined in that projects POM --&gt; &lt;dependency&gt; &lt;groupId&gt;com.thetus&lt;/groupId&gt; &lt;artifactId&gt;irisMDK&lt;/artifactId&gt; &lt;version&gt;0.1&lt;/version&gt; &lt;/dependency&gt; ... &lt;/dependencies&gt; .... &lt;/project&gt; </code></pre> <p>This will tell maven and eclipse that project A explicitly depends on that version of Project B. With M2Eclipse, if you have a matching groupId, artifactId, and version in your workspace and you have "Dependency Resolution" enabled, Project B's contents will automatically be built and included into Project A.</p> <p>Also, opening the Maven console in eclipse (console view->new console dropdown->new maven console) could help in debugging why project B isn't be picked up by Project A.</p>
    singulars
    1. This table or related slice is empty.
    1. POmaven build dependencies in Eclipse, multiple projects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBuffaloBuffalo
    1. USBuffaloBuffalo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am using that plugin, and have that in there, but unless I have build that jar it won't find it. I'd like it to build the Jar for me :)
      singulars
      1. PO
      1. USrybit
    2. COYou may need to change the scope to "compile" (i.e. not "system") for the workspace resolution to work. After making the changes outlined by @BuffaloBuffalo, you might also need to right click on the project and select "Maven->Update Project Configuration".
      singulars
      1. PO
      1. USjt.
    3. CO@jt Thats what I was just looking at--It also looks like in your example for A's pom, your dependency for B has a separate version than what you have defined in B's pom.xml's version
      singulars
      1. PO
      1. USBuffaloBuffalo
 

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