[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ohf-dev] problems launching stem.ui

Dan,

Actually, he's not the first, and there have always been problems with SWT
on the Mac. As a result, I have to agree with Sun's opposition to SWT. I'm
working with OHF on a 3 GB MacBook Pro, and do not approve of the way
Eclipse manages resources.

I'm not concerned with STEM, but I have been working to port the core of OHF
to Java EE (no OSGi), built using NetBeans 5.5.1 and 6.0m9. As a side note,
there are some packaging / dependency hassles with regard to OHF that I
would like to see addressed at some point (if anyone cares).

Vincent, you might consider porting the STEM UI to Swing if you want to see
it run well on the Mac OS.


-- 

Terrell Deppe
Chief Architect
Dairyland Healthcare Solutions




> From: Daniel Ford <daford@xxxxxxxxxxxxxxx>
> Reply-To: Open Healthcare Framework Mailing list <ohf-dev@xxxxxxxxxxx>
> Date: Wed, 13 Jun 2007 16:17:49 +0200
> To: Open Healthcare Framework Mailing list <ohf-dev@xxxxxxxxxxx>
> Subject: Re: [ohf-dev] problems launching stem.ui
> 
> Vincent,
>       this is great.  You're the first one to run on a Mac.  Hopefully,
> your work will help us release a Mac version shortly.
> 
> Dan
> 
> 
> 
>                  
>              Vincent David
>              <vincent@xxxxxxxx
>              pg.de>                                                     To
>              Sent by:                  Open Healthcare Framework Mailing
>              ohf-dev-bounces@e         list <ohf-dev@xxxxxxxxxxx>
>              clipse.org                                                 cc
>                  
>                                                                    Subject
>              06/13/2007 02:54          Re: [ohf-dev] problems launching
>              PM                        stem.ui
>                  
>                  
>              Please respond to
>               Open Healthcare
>              Framework Mailing
>                    list
>              <ohf-dev@eclipse.
>                    org>
>                  
>                  
> 
> 
> 
> 
> Dan,
> 
> thx for the feedback. I'm migrating the project recently to a PowerMac to
> see how STEM performes on more performative hardware. I do assume however
> that there is a problem with the swt.carbon integration with STEM. I will
> open up the bug-report after confirming my speculations and give more
> specific information.
> 
> Vincent
> 
> On Jun 13, 2007, at 2:16 PM, Daniel Ford wrote:
> 
>       Vincent,
>             could you be more specific about what "does not respond
>       properly"
>       means?  A  bug report in the Eclipse bugzilla
>       https://bugs.eclipse.org/bugs/ would also be most appreciated.
> 
>       Yes, it forks quite a few threads, this is controlled by the Eclipse
>       Jobs
>       API  The threads are performing I/O to retrieve the Lat/Long data for
>       the
>       countries in the model.  The data is stored independently for each
>       country
>       and retrieved in parallel.  This is expected.  You'll notice in the
>       Map
>       display that countries are added to the display one-at-a-time as
>       their I/O
>       completes, with smaller countries appearing before larger ones.  This
>       occurs once per country as their Lat/long data is cached.
> 
>       Typically, on Windows, virtual memory for most simulations requires
>       less
>       than a gigabyte.  The largest built-in scenario of the entire world
>       (ZZZ)
>       does require more than a gigabyte.  Also, the machine you run on
>       should
>       have 2 gigabytes of RAM to run STEM and function effectively as a
>       development environment.  The "large" memory requirements come from
>       the
>       level of detail represented in the model (thousands of nodes and tens
>       of)
>       thousands of labels and edges) and the extensive Lat/Long data
>       required to
>       draw resonably accurate maps.  We've made one attempt at reducing the
>       Lat/Long data, but I think we can do even more.
> 
>       Dan
> 
> 
> 
> 
> 
> 
>                    Vincent David
>                    <vincent@xxxxxxxx
>                    pg.de>
>       To
>                    Sent by:                  Open Healthcare Framework
>       Mailing
>                    ohf-dev-bounces@e         list <ohf-dev@xxxxxxxxxxx>
>                    clipse.org
>       cc
> 
> 
>       Subject
>                    06/13/2007 01:24          Re: [ohf-dev] problems
>       launching
>                    PM                        stem.ui
> 
> 
>                    Please respond to
>                     Open Healthcare
>                    Framework Mailing
>                          list
>                    <ohf-dev@eclipse.
>                          org>
> 
> 
> 
> 
> 
> 
>       Hi again,
> 
>       after getting the simulation actually up and running I come to the
>       impression, that the development version seems not to run fairly
>       stable
>       under MacOsX. While I had little problems getting the standalone app
>       running under WinXP the sim does not respond properly under MacOsX. I
>       can
>       start the sim normaly but after doing so I have problems accessing it
>       during simulation runtime. I can see in the "Activity Monitor" that
>       the
>       process forks of many threads (~20) and uses a lot of virt. Memory
>       (~1.5GB). I do not know if this is typical and would like some
>       feedback if
>       this is typical and how I can change this (I know about the -XmxNNNM
>       option
>       but not more).
> 
>       thx
> 
>       V
> 
>       P.S.:
> 
>       I think I will check out the sim on a PowerMac to see if performance
>       is the
>       key.
> 
>       On Jun 13, 2007, at 12:04 PM, Vincent David wrote:
> 
> 
>             Hi,,
> 
>             On Jun 13, 2007, at 11:15 AM, Daniel Ford wrote:
> 
>                   Vincent,
>                         I'm a bit handicaped helping you today as I'm
>       traveling
>                   (France) and
>                   I generally don't have access to a Mac.  However, did you
>       try
>                   opening)
>                   stem.product and then going to the "configuration" page
>       of the
>                   editor and
>                   then clicking on "Add Required Plugins"?
> 
>             I was not aware of this option yet. Nothing happens when
>       clicking on
>             the button. However, the swt-plugins I checked out formerly are
>             listed here and he appears to point properly at them. Looking
>       at the
>             "Manifest.mf" of "org.eclipse.swt.carbon.macosx" I found
>       following
>             error (marked in **):.
> 
>             Manifest-Version: 1.0.
>             Fragment-Host: org.eclipse.swt; bundle-version="[3.0.0,4.0.0)"
>             Bundle-Name: %fragmentName.
>             Bundle-Vendor: %providerName
>             Bundle-SymbolicName: org.eclipse.swt.carbon.macosx;
>       singleton:=true
>             Bundle-Version: 3.3.0.qualifier..
>             Bundle-ManifestVersion: 2
>             Bundle-Localization: fragment
>             Export-Package:
>             **The following needs to be false instead of true**
>              org.eclipse.swt.internal.carbon; x-internal:=true,
>              org.eclipse.swt.internal.cocoa; x-internal:=true,,
>              org.eclipse.swt.internal.opengl.carbon; x-internal:=true
>             Eclipse-PlatformFilter: (& (osgi.ws=carbon) (osgi.os=macosx) (|
>             (osgi.arch=x86)(osgi.arch=ppc)) )
>             Bundle-RequiredExecutionEnvironment: CDC-1.0/Foundation-1.0,
>              J2SE-1.3
> 
>             After patching I was acutally able of running the spanish flu
>       example
>             in the simulation ui. I do not know why this was necesssary and
>       what
>             I was actually doing... I'd appreciate further insight if
>       possible.
>       After further analysis I must revert my hypothesis regarding
>       patching. I.
>       guess it was the  "Add Required Plugins" recommonded  by Dan
> 
>             thx
> 
>             Vincent
> 
>                   Dan
> 
> 
> 
> 
> 
>                                Vincent David
>                                <vincent@xxxxxxxx
>                                pg.de>
>                   To
>                                Sent by:                  Open Healthcare
>                   Framework Mailing
>                                ohf-dev-bounces@e         list <
>                   ohf-dev@xxxxxxxxxxx>
>                                clipse.org
>                   cc
> 
>                   Subject
>                                06/13/2007 10:40          Re: [ohf-dev]
>       problems
>                   launching
>                                AM                        stem.ui
> 
> 
>                                Please respond to
>                                 Open Healthcare
>                                Framework Mailing
>                                      list
>                                <ohf-dev@eclipse.
>                                      org>
> 
> 
> 
> 
> 
> 
>                   Hi John,
> 
>                   thanks for your help. I solved the SWT-Proplem a step
>       further
>                   by importing:
> 
>                   org.eclipse.swt
>                   org.eclipse.swt.carbon.macosx
> 
>                   running the examples in:
> 
>                   org.eclipse.swt.examples
> 
>                   worked fine, so I'm confident reagrding this bundle.
>       However, I
>                   still
>                   become errors when trying to run "stem.product" of the
>                   "..stem.ui"
>                   package.
>                   I understand that there's something wrong with
>                   the .classvariable of SWT
>                   but I can't quite figure it out yet. Any help
>       appreciated.
>                   Error logs
>                   attached.
> 
>                   On Jun 12, 2007, at 10:48 PM, John Thomas wrote:
> 
>                         Vincent,
> 
>                         Thanks for figuring it out.  It looks like you are
>                   running on MacOS
>                         which is a platform that we have no experience
>       with.
>                         Once you have it running ,  any additional
>       instruction,
>                   that you can
>                         append here will be appreciated and I will update
>       the
>                   installation
>                         instructions in the Wiki  Or you could update the
>       Wiki,
>                   yourself if
>                         you
>                         like.
> 
>                         Thanks again.
>                         John
> 
>                         On 6/12/07, Vincent David <vincent@xxxxxxxxxxxxx>
>       wrote:
> 
> 
>                               On Jun 12, 2007, at 5:44 PM, Vincent David
>       wrote:
>                               Hello,
> 
>                               after configuring everything as far as
>       necessary to
>                   get the
>                               update.xml of
>                               the ..internal.data package running, I ran
>       into
>                   problems
>                               executing.
>                               "stem.product" of the ..stem.ui package. I
>       set
>                   options as
>                               instructed.
> 
>                               helping myself:
> 
>                               It appears that the swt-bundle is missing.
>       Checking
>                   out now. I:
>                               would like to
>                               recommend to mention this in the
>       documentation. It
>                   probably
>                               comes
>                               'naturally' if you're into Eclipse.
> 
>                               thx
> 
>                               Vincent
> 
> 
>                   Vincent David
> 
>                   MPI DS
> 
>                   Mail: vincent@xxxxxxxxxxxxx
>                   Phone: +49 551 5176 415
>                   Fax: +49 551 5176 439
>                   Cell:+49 163 7768977
>                   http://www.nld.ds.mpg.de
> 
> 
> 
> 
> 
>                   !SESSION 2007-06-12 18:39:26.844
>                   -----------------------------------------------
>                   eclipse.buildId=unknown
>                   java.version=1.5.0_07
>                   java.vendor=Apple Computer, Inc.
>                   BootLoader constants: OS=macosx, ARCH=x86, WS=carbon,
>       NL=en_US
>                   Framework arguments:  -product
>       org.eclipse.ohf.stem.ui.product
>                   Command-line arguments:  -product
>                   org.eclipse.ohf.stem.ui.product
> 
>       -data /Users/vincent/Documents/STEM/../runtime-stem.product
>                   -dev
> 
>       
> file:/Users/vincent/Documents/STEM/.metadata/.plugins/org.eclipse.pde.core/ste
> m.product/dev.properties
>                    -os macosx -ws carbon -arch x86 -debug -consoleLog
> 
>                   !ENTRY org.eclipse.osgi 2 0 2007-06-12 18:39:29.420
>                   !MESSAGE The following is a complete list of bundles
>       which are
>                   not
>                   resolved, see the prior log entry for the root cause if
>       it
>                   exists:
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:39:29.421
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.apt_1.0.0.v20070510-2000.jar
>        [369]
>                   was not resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2007-06-12
>                   18:39:29.421
>                   !MESSAGE Missing imported package
>                   org.eclipse.jdt.internal.compiler.tool_0.0.0.
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:39:29.421
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.tool_1.0.0.v_770.jar
>                   [370] was not
>                   resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2007-06-12.
>                   18:39:29.422
>                   !MESSAGE Missing Constraint:
>                   Bundle-RequiredExecutionEnvironment:.
>                   JavaSE-1.6
> 
>                   !ENTRY org.eclipse.osgi 4 0 2007-06-12 18:39:29.536
>                   !MESSAGE Application error
>                   !STACK 1
>                   java.lang.UnsatisfiedLinkError: no swt-carbon-3345 or
>                   swt-carbon in
>                   swt.library.path, java.library.path or the jar file
>                   at org.eclipse.swt.internal.Library.loadLibrary
>                   (Library.java:219).
>                   at org.eclipse.swt.internal.Library.loadLibrary
>                   (Library.java:151).
>                   at org.eclipse.swt.internal.C.<clinit>(C.java:21)
>                   at org.eclipse.swt.widgets.Display.createDisplay)
>                   (Display.java:943).
>                   at org.eclipse.swt.widgets.Display.create
>       (Display.java:937)
>                   at org.eclipse.swt.graphics.Device.<init>
>       (Device.java:119))
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:749)
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:740)
>                   at org.eclipse.ui.internal.Workbench.createDisplay
>                   (Workbench.java:498)
>                   at org.eclipse.ui.PlatformUI.createDisplay
>       (PlatformUI.java:161)
>                   at
> 
>       org.eclipse.ohf.stem.core.common.presentation.CoreEditorAdvisor
>                   $Application.start(CoreEditorAdvisor.java:109)
>                   at org.eclipse.equinox.internal.app.EclipseAppHandle.run
>                   (EclipseAppHandle.java:153)
>                   at
> 
>       
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
>                   (EclipseAppLauncher.java:106):
>                   at
> 
>       org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
>                   (EclipseAppLauncher.java:76).
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:363)
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:176)
>                   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:585)
>                   at org.eclipse.equinox.launcher.Main.invokeFramework
>                   (Main.java:504)
>                   at org.eclipse.equinox.launcher.Main.basicRun
>       (Main.java:443)
>                   at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
>                   at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
> 
>                   !ENTRY org.eclipse.osgi 2 0 2007-06-12 18:39:29.545:
>                   !MESSAGE The following is a complete list of bundles
>       which are
>                   not)
>                   resolved, see the prior log entry for the root cause if
>       it
>                   exists:),
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:39:29.545
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.apt_1.0.0.v20070510-2000.jar
>        [369]
>                   was not resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2007-06-12
>                   18:39:29.546
>                   !MESSAGE Missing imported package
>                   org.eclipse.jdt.internal.compiler.tool_0.0.0.
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:39:29.546
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.tool_1.0.0.v_770.jar
>                   [370] was not
>                   resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2007-06-12.
>                   18:39:29.547
>                   !MESSAGE Missing Constraint:
>                   Bundle-RequiredExecutionEnvironment:.
>                   JavaSE-1.6
>                   !SESSION 2007-06-12 18:50:22.200
>                   -----------------------------------------------
>                   eclipse.buildId=unknown
>                   java.version=1.5.0_07
>                   java.vendor=Apple Computer, Inc.
>                   BootLoader constants: OS=macosx, ARCH=x86, WS=carbon,
>       NL=en_US
>                   Framework arguments:  -product
>       org.eclipse.ohf.stem.ui.product
>                   Command-line arguments:  -product
>                   org.eclipse.ohf.stem.ui.product.
> 
>       -data /Users/vincent/Documents/STEM/../runtime-stem.product
>                   -dev
> 
>       
> file:/Users/vincent/Documents/STEM/.metadata/.plugins/org.eclipse.pde.core/ste
> m.product/dev.properties
>                    -os macosx -ws carbon -arch x86 -debug -consoleLog
> 
>                   !ENTRY org.eclipse.osgi 4 0 2007-06-12 18:50:25.002
>                   !MESSAGE Application error
>                   !STACK 1
>                   java.lang.UnsatisfiedLinkError: no swt-carbon-3345 or.
>                   swt-carbon in
>                   swt.library.path, java.library.path or the jar file
>                   at org.eclipse.swt.internal.Library.loadLibrary
>                   (Library.java:219).
>                   at org.eclipse.swt.internal.Library.loadLibrary
>                   (Library.java:151).
>                   at org.eclipse.swt.internal.C.<clinit>(C.java:21)
>                   at org.eclipse.swt.widgets.Display.createDisplay)
>                   (Display.java:943).
>                   at org.eclipse.swt.widgets.Display.create
>       (Display.java:937)
>                   at org.eclipse.swt.graphics.Device.<init>
>       (Device.java:119))
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:749)
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:740)
>                   at org.eclipse.ui.internal.Workbench.createDisplay
>                   (Workbench.java:498)
>                   at org.eclipse.ui.PlatformUI.createDisplay
>       (PlatformUI.java:161)
>                   at
> 
>       org.eclipse.ohf.stem.core.common.presentation.CoreEditorAdvisor
>                   $Application.start(CoreEditorAdvisor.java:109)
>                   at org.eclipse.equinox.internal.app.EclipseAppHandle.run
>                   (EclipseAppHandle.java:153)
>                   at
> 
>       
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
>                   (EclipseAppLauncher.java:106):
>                   at
> 
>       org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
>                   (EclipseAppLauncher.java:76).
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:363)
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:176)
>                   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:585)
>                   at org.eclipse.equinox.launcher.Main.invokeFramework
>                   (Main.java:504)
>                   at org.eclipse.equinox.launcher.Main.basicRun
>       (Main.java:443)
>                   at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
>                   at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
> 
>                   !ENTRY org.eclipse.osgi 2 0 2007-06-12 18:50:25.024:
>                   !MESSAGE The following is a complete list of bundles
>       which are
>                   not)
>                   resolved, see the prior log entry for the root cause if
>       it
>                   exists:),
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:50:25.024
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.apt_1.0.0.v20070510-2000.jar
>        [369]
>                   was not resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2007-06-12
>                   18:50:25.024
>                   !MESSAGE Missing imported package
>                   org.eclipse.jdt.internal.compiler.tool_0.0.0.
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-12 18:50:25.025
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.tool_1.0.0.v_770.jar
>                   [370] was not
>                   resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2007-06-12.
>                   18:50:25.025
>                   !MESSAGE Missing Constraint:
>                   Bundle-RequiredExecutionEnvironment:.
>                   JavaSE-1.6
>                   !SESSION 2007-06-13 10:27:11.555
>                   -----------------------------------------------
>                   eclipse.buildId=unknown
>                   java.version=1.5.0_07
>                   java.vendor=Apple Computer, Inc.
>                   BootLoader constants: OS=macosx, ARCH=x86, WS=carbon,
>       NL=en_US
>                   Framework arguments:  -product
>       org.eclipse.ohf.stem.ui.product
>                   Command-line arguments:  -product
>                   org.eclipse.ohf.stem.ui.product.
> 
>       -data /Users/vincent/Documents/STEM/../runtime-stem.product
>                   -dev
> 
>       
> file:/Users/vincent/Documents/STEM/.metadata/.plugins/org.eclipse.pde.core/ste
> m.product/dev.properties
>                    -os macosx -ws carbon -arch x86 -debug -consoleLog
> 
>                   !ENTRY org.eclipse.osgi 4 0 2007-06-13 10:27:14.257
>                   !MESSAGE Application error
>                   !STACK 1
>                   java.lang.UnsatisfiedLinkError: PTR_sizeof
>                   at org.eclipse.swt.internal.C.PTR_sizeof(Native Method)
>                   at org.eclipse.swt.internal.C.<clinit>(C.java:24)
>                   at org.eclipse.swt.widgets.Display.createDisplay)
>                   (Display.java:943).
>                   at org.eclipse.swt.widgets.Display.create
>       (Display.java:937)
>                   at org.eclipse.swt.graphics.Device.<init>
>       (Device.java:119))
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:749)
>                   at org.eclipse.swt.widgets.Display.<init>
>       (Display.java:740)
>                   at org.eclipse.ui.internal.Workbench.createDisplay
>                   (Workbench.java:498)
>                   at org.eclipse.ui.PlatformUI.createDisplay
>       (PlatformUI.java:161)
>                   at
> 
>       org.eclipse.ohf.stem.core.common.presentation.CoreEditorAdvisor
>                   $Application.start(CoreEditorAdvisor.java:109)
>                   at org.eclipse.equinox.internal.app.EclipseAppHandle.run
>                   (EclipseAppHandle.java:153)
>                   at
> 
>       
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
>                   (EclipseAppLauncher.java:106):
>                   at
> 
>       org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
>                   (EclipseAppLauncher.java:76).
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:363)
>                   at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>                   (EclipseStarter.java:176)
>                   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:585)
>                   at org.eclipse.equinox.launcher.Main.invokeFramework
>                   (Main.java:504)
>                   at org.eclipse.equinox.launcher.Main.basicRun
>       (Main.java:443)
>                   at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
>                   at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
> 
>                   !ENTRY org.eclipse.osgi 2 0 2007-06-13 10:27:14.287:
>                   !MESSAGE The following is a complete list of bundles
>       which are
>                   not)
>                   resolved, see the prior log entry for the root cause if
>       it
>                   exists:),
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-13 10:27:14.287
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.apt_1.0.0.v20070510-2000.jar
>        [369]
>                   was not resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2007-06-13
>                   10:27:14.288
>                   !MESSAGE Missing imported package
>                   org.eclipse.jdt.internal.compiler.tool_0.0.0.
>                   !SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-13 10:27:14.288
>                   !MESSAGE Bundle.
> 
>       update@plugins/org.eclipse.jdt.compiler.tool_1.0.0.v_770.jar
>                   [370] was not
>                   resolved.
>                   !SUBENTRY 2 org.eclipse.jdt.compiler.tool 2 0 2007-06-13.
>                   10:27:14.288
>                   !MESSAGE Missing Constraint:
>                   Bundle-RequiredExecutionEnvironment:.
>                   JavaSE-1.6
> 
>                   _______________________________________________
>                   ohf-dev mailing list
>                   ohf-dev@xxxxxxxxxxx
>                   https://dev.eclipse.org/mailman/listinfo/ohf-dev
> 
> 
> 
>             Vincent David.
> 
>             MPI DS
> 
>             Mail: vincent@xxxxxxxxxxxxx
>             Phone: +49 551 5176 415.
>             Fax: +49 551 5176 439
>             Cell:+49 163 7768977
>             http://www.nld.ds.mpg.de
> 
> 
> 
> 
> 
>             _______________________________________________
>             ohf-dev mailing list
>             ohf-dev@xxxxxxxxxxx
>             https://dev.eclipse.org/mailman/listinfo/ohf-dev
> 
>       Vincent David
> 
>       MPI DS
> 
>       Mail: vincent@xxxxxxxxxxxxx
>       Phone: +49 551 5176 415
>       Fax: +49 551 5176 439
>       Cell:+49 163 7768977
>       http://www.nld.ds.mpg.de
> 
> 
> 
> 
>       _______________________________________________
>       ohf-dev mailing list
>       ohf-dev@xxxxxxxxxxx
>       https://dev.eclipse.org/mailman/listinfo/ohf-dev
> 
> 
>       _______________________________________________
>       ohf-dev mailing list
>       ohf-dev@xxxxxxxxxxx
>       https://dev.eclipse.org/mailman/listinfo/ohf-dev
> 
> Vincent David
> 
> MPI DS
> 
> Mail: vincent@xxxxxxxxxxxxx
> Phone: +49 551 5176 415
> Fax: +49 551 5176 439
> Cell:+49 163 7768977
> http://www.nld.ds.mpg.de
> 
> 
> 
> 
> _______________________________________________
> ohf-dev mailing list
> ohf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ohf-dev
> 
> 
> _______________________________________________
> ohf-dev mailing list
> ohf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ohf-dev