Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow do I properly setup a multi-module Maven project with sliding release cycles
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRob Di Marco
    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. COHmm, even if the POMs for each sub project were independent, I'd still have them referred to from the toplevel pom so that the whole project could be built or opened by IDEA/Netbeans - which still gives the debugging issue or version mismatch. I suspect the problems I'm having are two fold - whilst they're released independently they're deployed together as a system, not separate standalone projects, and more in that when debugging, there's no version information available about WHAT version is running.
      singulars
      1. PO
      1. USMark Derricutt
    2. COOn further thought, I suspect the problems I'm facing with version ranges here is that our CI tool is building/installing the top-level module whenever ANY module is changed, which will install a -SNAPSHOT version of all modules, even if they're freshly released, but unmodified. If, as you suggest I remove the multi-module build and configure the build server to watch each module individually this should help solve the release issues.
      singulars
      1. PO
      1. USMark Derricutt
    3. CODefinitely break your modules into their own top-level projects. Modules are meant to be built and released together. Also, consider leveraging something like Hudson's automatic rebuilding as determined from Maven dependencies (http://weblogs.java.net/blog/johnsmart/archive/2008/11/managing_automa.html) to ensure changes in lower-level dependencies are automatically propagated and rebuilt with the higher-level ones.
      singulars
      1. PO
      1. USBrian Laframboise
 

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