On 22/01/2013 1:42 PM, Panagiotis Skintzos wrote:
On Tue, Jan 22, 2013 at 10:09 PM, Emily Gouge <[email protected]>wrote:
- In "Step 3- Update the product definition 3.Update the
<application>.product file.":
Another approach is to simply use the config file you created:
In "Configuration File" section, simply check "Use an existing config
file"
and supply the config.ini filepath.
Again, I tried this without any success. When I built the project using
the export Eclipse product wizard, it would not start successfully. The
start levels of the plug-ins specified in the config.ini file were not
reflected in the built config.ini file. I might have been doing
something
else wrong but I couldn't make it work.
I think it's kind of an issue of the product editor, as it's not very
clear. There are 4 tabs there for each platform.
You have to specify the config.ini for every platform you plan to export
to.
If I only want to export to windows do I have to supply a config file for
Mac? I provided a config.ini files for the windows then did the export to
windows and it did not work.
No, you certainly don't. I was just thinking that maybe you supplied a
config for windows (the last tab) and then you tried the rcp in linux.
This is not a big deal as I found a work around - I am more just curious
as to what's different about my setup (or what I might have been doing
wrong).
I now see that the path to your config.ini is "configuration\config.ini"
Is that a path relative to the workspace location?
I have my config.ini in the same folder as the product file, and the path
specified is relative to the workspace (the root path of all my plugins)
Perhaps that's the difference?
I tried a good many variations on where the config.ini resided and the
link in the product editor. Each time I get the following error when I
try to run my exported product.
java.lang.IllegalStateException: Unable to acquire application service.
Ensure that the org.eclipse.core.runtime bundle is resolved and started
(see config.ini).
Two more notes:
The first line of the config.ini displayed is not needed:
config.ini
osgi.bundles=org.eclipse.equinox.common.....
There are two "Step 3" in the doc
Step 1 - Download the Required Jar Files
Step 2 - Set up Eclipse Application and Target Platform
Step 3 - Create Customization Plug-In
Step 3 - Update the product definition
Step 4 - Run the Application
Thanks for this - I fixed these up and added a comment about the
config.ini file so others can try both configurations.
Emily
-Pana
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
