Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is an interesting question and one that doesn't have a simple solution. I'll try to describe a potential solution and also describe in a little bit more detail how JDT accomplishes incremental compilation.</p> <p>First, a bit about JDT: </p> <p>Yes, JDT does read class files for some of its information, but only for libraries that don't have source code. And this information is really only used for editing assistance (content assist, navigation, etc).</p> <p>JDT computes incremental compilation by keeping track of dependencies between compilation units as they are compiled. This state information is stored on disk and retrieved and updated after each compile. </p> <p>As a more complete example, let's say that after a full build, JDT determines that A.java depends on B.java, which depends on C.java.</p> <p>If there is a <em>structural change</em> in C.java (a structural change is a change that can affect outside files (e.g., adding/removing a non-private field or method)), then B.java will be recompiled. A.java will <em>not</em> be recompiled since there was no structural change in B.java.</p> <p>After this bit of clarification on how JDT works, here are some possible answers to your questions:</p> <ol> <li>Yes. This must be done through statically accessible global objects. JDT does this through the JavaCore and JavaModelManager objects. If you don't want to use global singletons, then you can access to your type store available through your plugin's Bundle activator instance. The e4 project does allow dependency injection, which is probably even better (but is not really a part of the core Eclipse APIs).</li> <li>I think persisting the information on the file system is your best bet. The only real way to determine incremental compile dependencies is to do a full build, so you need to persist the information somewhere. Again, this is how JDT does it. The information is stored in your workspaces' <code>.metadata</code> directory somewhere in the org.eclipse.core.resources plugin. You can have a look at the <code>org.eclipse.jdt.internal.core.builder.State</code> class to see the implementation.</li> </ol> <p>So, this may not be the answer you are looking for, but I think this is the most promising way to approach your problem.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the best approach to incremental compilation when building a DSL using Eclipse?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndrew Eisenberg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat's the best approach to incremental compilation when building a DSL using Eclipse?
      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. COThanks for the detailed explanation. I think you've more or less confirmed my suspicions about how it should be implemented, but it's useful to know how the Java plugin has approached the problem.
      singulars
      1. PO
      1. USTom G
 

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