[jbosstools-issues] [JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress

Max Rydahl Andersen (JIRA) issues at jboss.org
Thu Oct 1 08:20:01 EDT 2015


    [ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114138#comment-13114138 ] 

Max Rydahl Andersen commented on JBIDE-19568:
---------------------------------------------

The help menu is not available from Central unless you go open it.

If we want central to where users go and install things from why not make it easy to run check for updates ?


> Disable the "Check for update" button while a check for update is in progress
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-19568
>                 URL: https://issues.jboss.org/browse/JBIDE-19568
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>             Fix For: 4.3.x
>
>
> while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog.
> In error log it was reporting this:
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/.
> 	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> 	at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:483)
> 	at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
> 	at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284)
> 	at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191)
> 	at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378)
> 	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.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> 	at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> 	at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> 	at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> would have expected we told the user about this error.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list