Jetty configuration after update from 3.0 to 3.0.1
Hi,
I've upgrade my development environment in order to develop for the new release of RTC. I've changed the target platform but if I try to use Jetty Launch configuration to run my test environment I get these errors:
It seems that my launch still try to load something from old version. How can I fix this?
Thanks,
Michele
I've upgrade my development environment in order to develop for the new release of RTC. I've changed the target platform but if I try to use Jetty Launch configuration to run my test environment I get these errors:
[ERROR] 2011-09-26 11:10:39.546 - FrameworkManager: An error event has occurred involving the bundle "org.eclipse.core.resources_3.5.2.R35x_v20091203-1235 [178]".
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: org.eclipse.core.resources_3.5.3.R35x_v20100928-0452
...
[ERROR] 2011-09-26 11:10:40.608 - FrameworkManager: An error event has occurred involving the bundle "org.eclipse.core.filesystem_1.2.1.R35x_v20091203-1235 [442]".
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: org.eclipse.core.filesystem_1.2.2.R35x_v20100928-0452
It seems that my launch still try to load something from old version. How can I fix this?
Thanks,
Michele
One answer
I've find that in SDK there are some duplicated jars (with more than one version). I've removed these jar:
and now it runs. But I've another question: how can I run a repotool -addTables to test DB created using launch configuration? It's a standalone server db so do I have to use jts or ccm repotools?
Where is the db location configured? In launch configuration I can't see any reference to C:\testDB (which is a pre-defined value).
Thanks,
Michele
org.eclipse.core.filesystem.aix.ppc_1.0.0.R35x_v20091203-1235.jar
org.eclipse.core.filesystem.linux.x86_1.3.0.R35x_v20091203-1235.jar
org.eclipse.core.filesystem.linux.x86_1.3.1.R35x_v201000319-0930.jar
org.eclipse.core.filesystem.linux.x86_64_1.1.0.R35x_v20091203-1235.jar
org.eclipse.core.filesystem.macosx_1.2.0.R35x_v20091203-1235.jar
org.eclipse.core.filesystem.solaris.sparc_1.1.0.R35x_v20091203-1235.jar
org.eclipse.core.filesystem.win32.x86_1.1.0.v20080604-1400.jar
org.eclipse.core.filesystem.win32.x86_1.1.100.R35x_v20100928-0452.jar
org.eclipse.core.filesystem.win32.x86_64_1.1.0.v20090316-0910.jar
org.eclipse.core.filesystem_1.2.1.R35x_v20091203-1235.jar
org.eclipse.core.net.win32.x86_1.0.0.I20080909.jar
org.eclipse.core.resources_3.5.2.R35x_v20091203-1235.jar
org.eclipse.help.base_3.4.0.v201002111343.jar
org.eclipse.help.webapp_3.4.1.v20091009_35x.jar
org.eclipse.swt.gtk.linux.x86_3.5.2.v3557f.jar
org.eclipse.swt.win32.win32.x86_3.5.2.v3557f.jar
org.mortbay.jetty.server_6.1.15.v200905151201.jar
org.mortbay.jetty.util_6.1.15.v200905182336.jar
and now it runs. But I've another question: how can I run a repotool -addTables to test DB created using launch configuration? It's a standalone server db so do I have to use jts or ccm repotools?
Where is the db location configured? In launch configuration I can't see any reference to C:\testDB (which is a pre-defined value).
Thanks,
Michele