Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A couple of pointers:</p> <ul> <li>Gradle strictly separates the <em>logical</em> project hierarchy (the way Gradle organizes your build into a logical hierarchy of projects) from the <em>physical</em> directory layout. Just about any mapping is possible. (One exception that comes to mind is that you can't have two projects sharing the same project directory.)</li> <li>To implement a custom directory layout, you'll have to set <code>projectDir</code> for all projects, not just the root project. You should use relative paths, e.g. <code>rootProject.projectDir = new File(settingsDir, "../foo")</code> and <code>project(":sub1").projectDir = new File(rootDir, "bar")</code>. Here, <code>settingsDir</code> refers to the directory containing <code>settings.gradle</code>, and <code>rootDir</code> is a shorthand for <code>rootProject.projectDir</code>.</li> <li>To configure projects generically, you can recursively walk <code>(root)Project.children</code>. Note that <code>settings.gradle</code> and <code>build.gradle</code> use different types to represent a project - <a href="http://gradle.org/docs/current/javadoc/org/gradle/api/initialization/ProjectDescriptor.html" rel="noreferrer">ProjectDescriptor</a> and <a href="http://gradle.org/docs/current/dsl/org.gradle.api.Project.html" rel="noreferrer">Project</a>, respectively.</li> <li>Gradle has to be invoked from the directory containing <code>settings.gradle</code>, or a subdirectory thereof. From a usability perspective, it is therefore best to put <code>settings.gradle</code> into the root of the directory hierarchy.</li> </ul> <p>For more information, see <a href="http://gradle.org/docs/current/dsl/org.gradle.api.initialization.Settings.html" rel="noreferrer">Settings</a> in the <a href="http://gradle.org/docs/current/dsl/index.html" rel="noreferrer">Gradle Build Language Reference</a>, and the <a href="http://gradle.org/docs/current/userguide/userguide_single.html#multi_project_builds" rel="noreferrer">Multi-Project Builds</a> chapter in the Gradle User Guide.</p>
    singulars
    1. This table or related slice is empty.
    1. POHaving difficulty setting up Gradle multiproject build for existing repository layout
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter Niederwieser
    1. USPeter Niederwieser
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHaving difficulty setting up Gradle multiproject build for existing repository layout
      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. VTAcceptedByOriginator
    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. COFantastic, Peter, thanks. That's resolved a whole heap of misconceptions that I had about how this works. I'll post another answer below showing the final example that worked for me in case others are struggling in the same area.
      singulars
      1. PO
      1. USAndy McKibbin
    2. COGlad it helped. Correction: According to the docs, a property set with -P is also available in the settings script. I've edited my answer accordingly.
      singulars
      1. PO
      1. USPeter Niederwieser
 

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