Databases
StackOverflow2013
Postsdbo
POEclipse not starting after migration to new mac
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse not starting after migration to new mac
    primarykey
    data
    text
    <p>I just used the Migration Assistant to move my stuff to a new mac and now when I launch Eclipse, I'm getting a pop-up telling me to look at: </p> <pre><code>~/.eclipse/org.eclipse.platform_3.7.0_564163029/configuration/1343925478439.log </code></pre> <p>which contains:</p> <pre><code>!SESSION 2012-08-02 12:37:58.263 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/Me/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/Me/.eclipse_keyring -showlocation !ENTRY org.eclipse.osgi 4 0 2012-08-02 12:37:58.630 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) </code></pre> <p>I found <a href="https://stackoverflow.com/questions/2493415/i-am-getting-a-following-error-while-launching-my-eclipse">this question</a>: and tried adding the following to /Applications/eclipse-indigo/Eclipse.app/Contents/MacOS/eclipse.ini:</p> <pre><code>-Dosgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@ </code></pre> <p>but it still didn't work. I also tried running eclipse from the command line with the -clean option:</p> <pre><code>/Applications/eclipse-indigo/eclipse -clean </code></pre> <p>Any other ideas? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USsprugman
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEclipse not starting after migration to new mac
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEclipse not starting after migration to new mac
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEclipse not starting after migration to new mac
      1. USJanne Aukia
      1. VTFavorite
    1. This table or related slice is empty.
 

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