Bug #1185
RCP: 0.7.7, automatic update bug at second launch
Statut: | Closed | Début: | 11/12/2014 | |
---|---|---|---|---|
Priorité: | Normal | Echéance: | ||
Assigné à: | - | % réalisé: | 100% |
|
Catégorie: | Update | Temps passé: | - | |
Version cible: | TXM 0.7.7 |
Description
- Deuxième lancement de TXM-0.7.7
- la splash et sa progression se lancent tout de suite
- stacktrace dans la console au démarrage :
Démarrage de TXM 0.7.7 (201412051011)... Moteur de recherche lancé en mode mémoire. Moteur statistique lancé.connecté. Chargement des sous-corpus et des partitions...Terminé. Prêt. org.eclipse.core.runtime.OperationCanceledException at org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:370) at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:208) at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:66) at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:88) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addURL(TXMUpdateHandler.java:248) at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addDefaultUpdateSites(TXMUpdateHandler.java:210) at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.execute(TXMUpdateHandler.java:85) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:330) at org.txm.rcpapplication.ApplicationWorkbenchAdvisor$3$1.run(ApplicationWorkbenchAdvisor.java:561) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:167) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:165) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.txm.rcpapplication.Application.run(Application.java:152) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) No update available.
Solution¶
Only Provision exceptions were catch, all exceptions are catched now
Validation test¶
- Install TXM
- start and quit TXM once
- Re-start TXM :
- if no update available the "No update available." console message appears
- MD : OK Linux64
- if there is an update and
- if your not connected : the "......." console message appears
- if your connected : the update dialog should open
- if no update available the "No update available." console message appears
Historique
#1 Mis à jour par Matthieu Decorde il y a presque 11 ans
- Description mis à jour (diff)
- % réalisé changé de 0 à 80
#2 Mis à jour par Matthieu Decorde il y a presque 11 ans
- Statut changé de New à Feedback
#3 Mis à jour par Matthieu Decorde il y a plus de 10 ans
- Description mis à jour (diff)
#4 Mis à jour par Sebastien Jacquot il y a plus de 10 ans
Successfully checked for the "if no update available the "No update available." console message appears" part.
Need an online update to check the other part.
#5 Mis à jour par Matthieu Decorde il y a plus de 10 ans
- Description mis à jour (diff)
#6 Mis à jour par Matthieu Decorde il y a plus de 4 ans
- Statut changé de Feedback à Closed
- % réalisé changé de 80 à 100