| Re: [udig-dev] Development environment |
Morning Jody,
Yes, on my Windows 64 machine the uDig application started.
On OSX, the problem is "java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM" but that is not important. It's not my main development machine anyway.
Thanks a lot.
-
Ivan
Date: Thu, 30 Jan 2014 15:54:27 +1100
Subject: Re: [udig-dev] Development environment
From: jody.garnett@xxxxxxxxx
To: lucena_ivan@xxxxxxxxxxx
CC: udig-dev@xxxxxxxxxxxxxxxxAfternoon Ivan:What is a good time of day to help you via IRC or Skype?The Eclipse "OSGi" runtime is very careful about compatibility and configuration when starting up. In this case either the forms jar was not available, or it did not match the expected version and was thus not loaded. This step you are stuck on is the most maddening thing about Eclipse RCP, often you can get things running from within Eclipse, and then export and be stuck back here at startup issues.The steps I do to check what is missing, and why, are to go to the run configuration (which was generated when you clicked "run" on the udig.product file).This dialog has 4 tabs, the one we are interested in is the *Plugins* tab, and the **Validate Plugins** button. This button performs the same checks that are preformed when the application starts up, and more importantly gives you a relatively easy tree, showing what plugin prevented which other plugin from starting.The other button of interest is **Add Required Plugins** that can act as a band aid, allowing you to launch, even if the application did not list everything it needed to start up.I apologise for this slow start :( We have been messing with our dependencies in order to migrate from jars to plugins a bit more.Jody GarnettOn Thu, Jan 30, 2014 at 2:10 AM, Ivan Lucena <lucena_ivan@xxxxxxxxxxx> wrote:Hi there,
It's me again. The guy who cannot build nDig in Eclipse.
After correcting what I was doing wrong I have the project on Eclipse Indigo Win64 and I still getting the same error when I tried to Launch the udig.product application. Here is the log file:
!SESSION 2014-01-29 09:45:27.035 -----------------------------------------------Command-line arguments: -product org.locationtech.udig.product -data C:\Users\ilucena\workspace/../runtime-udig.product -dev file:C:/Users/ilucena/workspace/.metadata/.plugins/org.eclipse.pde.core/udig.product/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog
eclipse.buildId=unknown
java.version=1.7.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.locationtech.udig.product
!ENTRY org.eclipse.equinox.app 0 0 2014-01-29 09:45:27.834!ENTRY org.eclipse.osgi 2 0 2014-01-29 09:45:27.906
!MESSAGE Product org.locationtech.udig.product could not be found.!SUBENTRY 1 org.eclipse.osgi 2 0 2014-01-29 09:45:27.906
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!MESSAGE Bundle reference:file:/C:/Users/ilucena/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.help.ui_3.5.101.r37_20110819.jar was not resolved.
!SUBENTRY 2 org.eclipse.help.ui 2 0 2014-01-29 09:45:27.906!ENTRY org.eclipse.osgi 2 0 2014-01-29 09:45:27.908
!MESSAGE Missing required bundle org.eclipse.ui.forms_[3.5.0,4.0.0).!SUBENTRY 1 org.eclipse.osgi 2 0 2014-01-29 09:45:27.909
!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 2 org.eclipse.help.ui 2 0 2014-01-29 09:45:27.909
!MESSAGE Bundle org.eclipse.help.ui_3.5.101.r37_20110819 [42] was not resolved.!ENTRY org.eclipse.osgi 4 0 2014-01-29 09:45:27.910
!MESSAGE Missing required bundle org.eclipse.ui.forms_[3.5.0,4.0.0).
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:242)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
If I understand it right, the org.locationtech.udig.product.jar if not generated because the compilation cannot find packages org.eclipse.ui.form_*.
Is that right?
Why is that?
Is there something outdated on the target platform definition or something has changed on the repository website?
Can I just grab the missing packages from here [http://archive.eclipse.org/technology/babel/]? But how to include that to my project?
Any suggestions?
Best regards,
Ivan> From: lucena_ivan@xxxxxxxxxxx
> To: jody.garnett@xxxxxxxxx
> Date: Tue, 28 Jan 2014 13:24:45 -0500
> CC: udig-dev@xxxxxxxxxxxxxxxx
> Subject: Re: [udig-dev] Development environment
>
> Jody,
>
> I already posted my mvn error messages. Thanks.
>
> I have followed the steps again with the tips from Frank and Jody and my project seems to be correct now. But I am gstill having the same error when trying to launch the application, in both Win64 and osx32 (I might try linux64 too). So I am switching to Eclipse Indigo to see how it goes. Currently I am "Loading Target Platform" on Eclipse Indigo on Win64, JRE 1.7.
>
> Regards,
>
> Ivan
>
> ________________________________
> > Date: Tue, 28 Jan 2014 10:38:14 +1100
> > Subject: Re: [udig-dev] Development environment
> > From: jody.garnett@xxxxxxxxx
> > To: lucena_ivan@xxxxxxxxxxx
> > CC: udig-dev@xxxxxxxxxxxxxxxx
> >
> > 2. Download stuff
> >
> > mvn clean install -f pom-libs.xml
> >
> > After getting an error, I end up downloading a jar file "by hand"
> > copying the file path to a browser and then, saving it to the path
> > specified by the script. I ran the same mvn command again and at the
> > end it was all "success".
> >
> > What was the error you received?
> >
> > Option - Eclipse Build
> >
> > The instructions doesn't really sat what version of Eclipse or JRE to
> > use. Does it matter? I am trying in a Windows 7 64Bit and a OSX 10.6
> > 32Bit, Eclipse Kepler release 1, JRE 7 and 6 respectively.
> >
> > Previously we used Eclipse 3.7.2 - but my understanding is that the
> > "target platform" approach now allows us to use a newer Eclipse.
> >
> > 1. Import the targets/indigo project into workspace.
> >
> > Forgive my ignorance, but it seems like I cannot just import that thing
> > without creating a project first. Right? What kind of project that
> > would be? I tried several different options but let's say it is suppose
> > to be a regular empty Java project.
> >
> > That is what I did. I created a regular Java project and I imported
> > then I found and imported the file /udig/extras/targets/indigo" to that
> > new project. Is it the right thing to do?
> >
> > There is a wizard to import existing projects. The checkout includes
> > the .project and .classpath files needed to define a rather long list
> > of projects (one for each plugin making up the application).
> >
> > It was my intention that you only import this one project (that
> > contains the project file).
> > Should probably stop here (or backtrack) until you can sort out this step...
> >
> > 2. Open up udig-indigo-target.target and click on Set as Target Platform
> >
> > That takes forever but It concluded successful on both system, after
> > stop and continuing it a couple of times by closing Eclipse. The only
> > difference is that I only have 2296 plug-ins available on the first
> > line instead of 2306. Is that a problem?
> >
> > I am not sure will have to check, we have been working to make more use
> > of the target platform (and less use of downloading jars).
> >
> > 3. Save a copy of the target-platform locally
> >
> > I don't understand what it is, but I did it anyway. Does it means that
> > I can close my current project where I have imported all that stuff and
> > go and open the local copy and follow the rest of instructions from
> > there? Or is ti only a place to download the external jars?
> >
> > I am not sure either, sounds like I have to try out the instructions
> > again myself.
> >
> >
> > 4. Once the target platform is finished you can import the remaining
> > uDig projects.
> >
> > A little bit of detailing here would be nice. I don't know how to
> > switch to the local project (if here is one) so I just select the
> > Import> Existing Projects into Workspace on the same project that I
> > started earlier.
> >
> > Should I check the box that says Copy projects into workspace?
> >
> > No, we are trying to leave the projects in your checkout location (so
> > any changes you made will be seen by git).
> >
> > Ivan I will be available on IRC (or Skype) if you need help getting set up.> _______________________________________________
> udig-dev mailing list
> udig-dev@xxxxxxxxxxxxxxxx
> https://locationtech.org/mailman/listinfo/udig-dev