Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You're going to need to do some creative "Maven-ing," as I just made up the term to describe it. (In reality it probably isn't creative at all, but I'm a bit of a Maven newbie myself, so it stumped me for a while too).</p> <p>You're right in a sense, the GWT comipler <em>is</em> looking for the inherited module's <em>source</em> on the classpath when it tries to compile your "main" module. To achieve this, you will need to add a dependency, to the main module's pom, on the library module's sources (strictly for the compile phase).</p> <p>Something like this:</p> <pre><code>... &lt;artifactId&gt;main-module&lt;/artifactId&gt; ... &lt;dependency&gt; &lt;groupId&gt;library-group&lt;/groupId&gt; &lt;artifactId&gt;library-artifact&lt;/artifactId&gt; &lt;type&gt;jar&lt;/type&gt; &lt;version&gt;0.1-SNAPSHOT&lt;/version&gt; &lt;classifier&gt;sources&lt;/classifier&gt; &lt;scope&gt;compile&lt;/scope&gt; &lt;/dependency&gt; ... </code></pre> <p>Now, where you get those sources from can differ. If you're just trying to do this from an IDE, like Eclipse, this is probably enough because the m2eclipse plugin is smart enough to know where to get those sources (if the library-module is also in your workspace). If this is your actual build process, then you will need to modify the library-module's pom to produce the -sources artifact along with the standard "library-artifact." So you'll end up with both:</p> <pre><code>library-artifact-0.1-SNAPSHOT.jar </code></pre> <p>and</p> <pre><code>library-artifact-0.1-SNAPSHOT-sources.jar </code></pre> <p>Hopefully it's more clear how the gwt-maven-plugin proceeds from that point. </p> <p>Almost forgot, the one other question I've answered here might be of some use as well: <a href="https://stackoverflow.com/questions/6026218/gwt-project-structure/6044970#6044970">GWT Project Structure</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POGWT getting an inherited module on the compiler's classpath
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJason482
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the response. Some additional clarification on our situation: We are indeed using Eclipse and currently have our application set up as a single Eclipse project. Within this project we have several gwt modules that make up different areas of our application. It made sense to have another, entry-point-less module to house shared resources for the other modules to inherit. We figured it would require us to set up a new project for our application to depend on, which I think is what you are describing. But, is there a way to locate the resource module within the primary project?
      singulars
      1. PO
      1. USmreynolds0404
    2. COAh, I missed the "single project" part, initially. Indeed, I'm describing a separate project/artifact. However, you should be able to do it just like you have inheritance set up between your other GWT modules. GWT module A's gwt.xml, you'd have "<inherits name='some.shared.package.ModuleB' />", where Module B is your shared GWT module (with a gwt.xml file, but entry-point-less, if you want). Now, it _should_ be easy for the GWT compiler to find the source for B, since they are all in the same Eclipse project. Have you tried turning Maven debug stack traces on (-X)?
      singulars
      1. PO
      1. USJason482
 

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