We have tried with other systems, and we have changed the date in order to have 
the same scenary as we had before, and we have not got any error, maybe it was 
a error in our systems and not a Equinox fault. I have tried with the version 
3.5 and it worked fine, so I am going to try again and if I get again the same 
error I will open a error.

 

Thank you again

 

David

 

De: [email protected] [mailto:[email protected]] En 
nombre de Thomas Watson
Enviado el: martes, 30 de junio de 2009 15:31
Para: Equinox development mailing list
Asunto: RE: [equinox-dev] Problem after updating timezone Equinox v3.4

 

I cannot think of anything that would cause issues with dates. I suggest you 
open a bug so we can gather the necessary information and track the issue. Have 
you tried 3.5?

Tom



Inactive hide details for "David Conde" ---06/30/2009 01:42:15 AM---Hello 
Tom,"David Conde" ---06/30/2009 01:42:15 AM---Hello Tom,



From:


"David Conde" <[email protected]>



To:


"'Equinox development mailing list'" <[email protected]>



Date:


06/30/2009 01:42 AM



Subject:


RE: [equinox-dev] Problem after updating timezone Equinox v3.4

  _____  





Hello Tom,

Thank you for your answer, but the problem continues being very rare, because 
of a workmate of mine, tried yesterday launching Equinox by console in basic 
mode with the version org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar, and it 
did not work at all, with the same error and Exception that I got. It is very 
strange because he did not launch the timezone updater (tzupdater.jar), and he 
got the same Exception in logFile with the same results.

Finally, today, just a couple of minutes ago, I tried again with the same 
command  (java -jar org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar –console) 
and it worked fine, as the same way, my workmate have launched the same command 
and doing nothing new regarding what it was done yesterday we have got good 
result and Equinox starting as normal as it did before yesterday.

Could it be a problema with the any dates in Equinox?

David
 
De: [email protected] [mailto:[email protected]] En 
nombre de Thomas Watson
Enviado el: lunes, 29 de junio de 2009 15:48
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Problem after updating timezone Equinox v3.4

I would expect this error message if you are not specifying the configuration 
option eclipse.ignoreApp=true

Without this option we are expecting the full eclipse runtime to be active and 
available to start an eclipse application.

Tom



Inactive hide details for "David Conde" ---06/29/2009 06:13:41 AM---Hi,"David 
Conde" ---06/29/2009 06:13:41 AM---Hi, 



From:


"David Conde" <[email protected]>



To:


"'Equinox development mailing list'" <[email protected]>



Date:


06/29/2009 06:13 AM



Subject:


[equinox-dev] Problem after updating timezone Equinox v3.4

  _____  





Hi,

I wrote about this in my previous thread, but I think it is better to write 
this thread separately to the other one, because of the other one was about 
PermissionAdmin service having nothing to do with this case:

Trying to launch Equinox v3.4 with security features I got the next exception:

Exception in thread "main" java.lang.NoClassDefFoundError: ûjar

It was very rare because I tried to launch the security command as I did before 
trying with Equinox v3.3 and Equinox v3.4 (when they working fine)

I was looking for the solution and I tried to update the dates with the 
timezone update by SUn (-jar tzupdater.jar), following the information which I 
found in Internet.

After that, I reboot my PC and then I tried to launch Equinox v3.3 without 
security and with security and worked fine, however, when I tried to launch 
Equinox v3.4 by console, with either basic or security features, did not work 
at all, getting the next exception in the logfile:


!ENTRY org.eclipse.osgi 4 0 2009-06-29 12:51:05.562
!MESSAGE Application error
!STACK 1
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)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.core.runtime.adaptor.EclipseStarter.main(EclipseStarter.java:150)


have these problem happen to anyone?


My used commands are as I used before, they were tried and were working fine, 
so I do not really know what happens now.

BASIC LAUNCHING:

java -jar org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar –console

SECURITY LAUNCHING:

Java 
-Declipse.security=org.eclipse.osgi.framework.internal.core.FrameworkSecurityManager
 -jar org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar –console



So I do not know what I am missing?

It is very strange case because of I tried with the same commands and I was 
fine a couple of months ago, so I think it is a problem related to updater and 
Equinoxv3.4.


Thank you in advance for any idea_______________________________________________
equinox-dev mailing list
[email protected]
 <https://dev.eclipse.org/mailman/listinfo/equinox-dev> 
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev



<<image001.gif>>

<<image003.png>>

<<image004.png>>

<<image005.png>>

<<image006.png>>

_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to