Re: [udig-dev] alpha blog post and release notes

[Jody Garnett <jody.garnett@xxxxxxxxx>]

Running this same test with uDig 1.4.0 SDK ...

- The target platform configuration and plugin validation went smoothly

- The application refuses to start - with a different error (java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError).

I am afraid I am not doing something right when testing the SDK

Andrea have you previously used the 1.4.0 SDK?

Jody Garnett

On Sun, Dec 8, 2013 at 5:26 PM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

Afternoon Andrea:

I am trying to catch up with your testing, and see if I can fill in the gaps from your email.

DOWNLOAD

Environment: OSX 10.9, JDK 1.6.0_51-b11_457

Verdict: works for me

- started with a fresh udig project folder (since I would not expect the previous one to load)

- release notes html seemed okay

- application starts

- short cuts from welcome page to online help work correctly

- application shows both shape files and raster data (tested with data_1_3 download)

- application about shows JAI plugin included

SDK

Environment: IDE Elipse 3.7.2, Platform OSX 10.9, JDK 1.6.0_51-b11-457, set up from a completely new workspace with no previous configuration

Verdict: does not work even with extensive workarounds and experimentation

0. Set up with a completely new workspace, no previous configuration

- Set up

1. Setting up target platform

This is an "includes everything" target platform: while I expect it to include SWT I was unclear if it was going to include JAI and ImageIO.

I could not quite remember how to set this up, previously I made a new target platform and added the directory of the current eclipse and the directory of the target platform.

a) Setting Target Platform using "Features" - scans a directory for features (have not used this before)

- Mostly worked, but "Problems occurred getting the plug-ins in this container: required plug-in could not be found: org.eclipse.swt.cocoa.macosx.x86_64.source

b) Setting Target Platform using Directory - this one scans for plugins in the provided directory

- Detected 626 plugins available

2. Testing sample application

- Performed usual test, selected org.locationtech.udig from the plug-ins view and imported as source plugin

- The result built without error

- open udig.product and click "Launch an Eclipse Application" failed to start ...

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)

This is the usual invalid dependency exception ... the only other exceptions are:

!ENTRY org.eclipse.core.runtime 4 0 2013-12-08 17:10:37.590

!MESSAGE FrameworkEvent ERROR

!STACK 0

org.osgi.framework.BundleException: The bundle "org.eclipse.core.runtime_3.7.0.v20110110 [2]" could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.contenttype; bundle-version="[3.3.0,4.0.0)"

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)

at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.eclipse.equinox.p2.reconciler.dropins 4 0 2013-12-08 17:10:37.602

!MESSAGE FrameworkEvent ERROR

!STACK 0

org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.p2.reconciler.dropins_1.1.100.v20110815-1419 [283]" could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.p2.touchpoint.eclipse; bundle-version="1.0.0"

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)

at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

So hunting through the Validate Plugins list I can see we are missing a of dependencies. I am used to this list providing missing plugin dependencies. This time it was all "Missing Constraint Import-Package:"

- com.ibm.icu.text

- com.ibm.icu.util

- javax.media.jai

- javax.media.jai.iterator

- javax.media.jai.operator

- javax.media.jai.*

- javax.servlet.http

- javax.servlet.jsp

- javax.servlet.*

- and a great deal more

So our SDK release did not include enough to be a stand alone target platform.

Changing the target platform to include the hosting IDE did not help, it then showed duplicates for any of the translation plugins, and anything requiring JAI still did not load.

Jody Garnett

On Sat, Dec 7, 2013 at 12:22 AM, andrea antonello <andrea.antonello@xxxxxxxxx> wrote:

> I am confused Andrea. It should be very much usable - if not we make it
> again.
>
> If is not usable it should not be on the website.

I tried to both build it and donwload it and in both cases when I
started it up, it did definitely not look like uDig.

Am I the only one experiencing this? I should not have conflicting
workspaces but you never know.

Cheers,
Andrea