Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-devel] packaging udig

Sounds good. If I can ask you to retest after the code sprint; I spent a little time with the Activator in the imageio plugin (trying to make it fail properly when GDAL could not be found; previously it just "returned" from its startup method (causing amazingly confusing strack traces). Now it throws a nice exception that should appear in the log.

Jody

On Wed, Jan 14, 2009 at 6:30 AM, Graham Davis <gdavis@xxxxxxxxxxxxxxx> wrote:
Emily helped me out.   I just needed a different JRE with Mr.Sid support.  Then I needed to update the udig.product I was exporting to specifically use this JRE.  Looks like I got it working now (thanks Emily!).

Graham.



Graham Davis wrote:
Jody and others,

I've managed to get the application exporting after installing Eclipse 3.4.1 from scratch.  My problem now is that the uDig application that is exported does not seem able to recongnize mr. sid files.  When I run uDig from Eclipse I can load sid files fine.  But the exported version cannot.  I'm guessing this isn't including in the regular udig feature?  How can I add this support to my exported application?  Thanks,

Graham.

Graham Davis wrote:
I can see I have this plugin:
org.eclipse.equinox.launcher_1.0.100.v20080509-1800

but not the version it says is missing.  I can't find any reference to the missing version so I'm not sure where it is pulling that from.  Any ideas?

Graham.


Graham Davis wrote:
Hi Jody, thanks for the help.

I managed to copy the deta-pack from the extras into the eclipse directory from #1.  For #2, I'm not sure what (if anything) needs changing.  My target platform checkbox says "build target platform based on the target's installed plug-ins" and it is checked.  Is this not correct?

Now when I try to export the product by clicking the "Eclipse product export wizard" link on the udig.product overview page, I get the following error right away:

Problems during export
 Unable to find plug-in: org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. Please check the error log for more details.
 Unable to find plug-in: org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. Please check the error log for more details.

I'm not sure what this is, or where it is set.  Any more ideas?

Graham.


Jody Garnett wrote:
Hi Graham:

I too have been having fun exporting out a custom application; you will find over the course of the last week I have tried to fix up the features that go into the custom application so that it works on Eclipse 3.4.1. You will also notice I found the solution to your trouble...

1. unpack the rcp delta pack into your eclipse directory (not into dropins!)
2. when you define the target platform you have to look at the check mark at the top of the dialog that excludes entries that do not work for the current platform

With these in mind you should be okay - please advise?
Jody

Graham Davis wrote:
I'm trying to package a version of udig with my new custom plugin included (which I've created a feature for).  When I get to the point of trying to export the product , it gets most of the way through then completes saying there is a log of errors.  I can see hundreds of warnings from all the various plugins, but don't see any glaring errors.  When I try running my exported application, I get a "Workbench early startup" error right away with this error:

An internal error occurred during: "Workbench early startup".
Unresolved compilation problems:
  The type org.eclipse.swt.widgets.Display cannot be resolved. It is indirectly referenced from required .class files
  The type org.eclipse.swt.widgets.Shell cannot be resolved. It is indirectly referenced from required .class files
  The type org.eclipse.swt.graphics.Image cannot be resolved. It is indirectly referenced from required .class files
  The import org.eclipse.swt.widgets.Display cannot be resolved
  The method getDisplay() from the type IWorkbench refers to the missing type Display
  The method getShell() from the type Window refers to the missing type Shell
  Display cannot be resolved
  Display cannot be resolved to a type
  The method getDisplay() from the type IWorkbench refers to the missing type Display
  Display cannot be resolved
  The method getShell() from the type Window refers to the missing type Shell

I get the same problem if I simply try to export the udig.product application from net.refractions.udig.  Is there something I am missing or doing wrong?










--
Graham Davis
Refractions Research Inc.
gdavis@xxxxxxxxxxxxxxx



Back to the top