Databases
StackOverflow2013
Postsdbo
POCode completion issues with the Scala-IDE and Eclipse Juno
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCode completion issues with the Scala-IDE and Eclipse Juno
    primarykey
    data
    text
    <p>I'm using Eclipse Juno with the Java (Java build 1.7.0_05-b05 64bit) and Scala-IDE plugin (Scala IDE for Eclipse 2.1.0.nightly-2_09-201207100348-f1d9c23 org.scala-ide.sdt.feature.feature.group scala-ide.org).</p> <p>Below are my custom settings for Eclipse eclipse.ini:</p> <pre><code>-vmargs -Dosgi.requiredJavaVersion=1.7 -Dhelp.lucene.tokenizer=standard -Xss8m -Xms256m -Xmx1536m -XX:PermSize=64m -server -Xverify:none -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+DoEscapeAnalysis -XX:+UseCompressedOops </code></pre> <p>Every-time I try to use code completion Eclipse throwing me 2 error windows:</p> <pre><code>The 'Code Recommenders Calls Proposals' proposal computer from the 'org.eclipse.recommenders.completion.rcp.calls' plug-in did not complete normally. The extension has thrown a runtime exception. </code></pre> <p>and</p> <pre><code>The 'Code Recommenders Overrides Proposals' proposal computer from the 'org.eclipse.recommenders.completion.rcp.overrides' plug-in did not complete normally. The extension has thrown a runtime exception. </code></pre> <p>My scala-ide log below shows:</p> <pre><code>[Xlint:cantFindType] 2012-07-10 15:37:29,404 ERROR [main] - System.err - [org.eclipse.jdt.launching] error can't determine modifiers of missing type org.eclipse.pde.internal.ui.wizards.imports.PluginImportHelper when weaving type org.eclipse.jdt.launching.JavaRuntime when weaving classes when weaving [Xlint:cantFindType] </code></pre> <p>Is there any way to fix this?</p> <p>Thank you.</p> <p><strong>UPDATE 1</strong>: After disabling code Recommenders I'm getting a different error in my Slaca-Ide log:</p> <pre><code>2012-07-10 16:10:24,342 ERROR [main] - System.err - [org.eclipse.jdt.debug.ui] error can't determine modifiers of missing type org.eclipse.pde.internal.ui.wizards.imports.PluginImportHelper when weaving type org.eclipse.jdt.internal.debug.ui.actions.ToggleBreakpointAdapter when weaving classes when weaving [Xlint:cantFindType] </code></pre> <p>but the scala code completion now works ok</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTimka
    1. USTimka
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCode completion issues with the Scala-IDE and Eclipse Juno
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCode completion issues with the Scala-IDE and Eclipse Juno
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCode completion issues with the Scala-IDE and Eclipse Juno
      1. USFabian
      1. VTFavorite
    1. COPlease post this on [scala-ide-user](https://groups.google.com/forum/?fromgroups#!forum/scala-ide-user)
      singulars
      1. POCode completion issues with the Scala-IDE and Eclipse Juno
      1. USkiritsuku
    2. CO@sschaef: Thanks - done:)
      singulars
      1. POCode completion issues with the Scala-IDE and Eclipse Juno
      1. USTimka
 

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