[jbosstools-issues] [JBoss JIRA] (JBIDE-26621) Cannot install anything from RH Central Update

Ondrej Dockal (Jira) issues at jboss.org
Tue May 28 08:50:00 EDT 2019


     [ https://issues.jboss.org/browse/JBIDE-26621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Dockal closed JBIDE-26621.
---------------------------------


Verified on 12.12.0.AM1-v20190520-0258-B4567. Closing.

> Cannot install anything from RH Central Update
> ----------------------------------------------
>
>                 Key: JBIDE-26621
>                 URL: https://issues.jboss.org/browse/JBIDE-26621
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central-update
>    Affects Versions: 4.11.0.Final
>         Environment: Any
>            Reporter: Ondrej Dockal
>            Assignee: Jeff MAURY
>            Priority: Blocker
>             Fix For: 4.12.0.AM1
>
>
> Cannot install anything from Central Software/Update due to:
> {code}
> eclipse.buildId=12.11.0.GA-v20190329-0120-B4247
> java.version=1.8.0_201
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -product com.jboss.devstudio.core.product
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.mylyn.discovery.core
> Error
> Wed Apr 03 10:37:25 CEST 2019
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> org.eclipse.core.runtime.CoreException: IO failure: cannot load discovery directory
> 	at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:115)
> 	at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> 	at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> 	at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:116)
> 	at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> 	at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.io.FileNotFoundException: https://devstudio.redhat.com/12/staging/updates/discovery.earlyaccess/12.11.0.GA/devstudio-directory.xml
> 	at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:494)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:451)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:286)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:175)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.stream(P2TransportService.java:96)
> 	at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.stream(WebUtil.java:180)
> 	at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.readResource(WebUtil.java:98)
> 	at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:92)
> 	... 6 more
> {code}
> The url does not exist. I believe this is because of removed staging bits and that fact that central update points there... Should not it be pointing to stable?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jbosstools-issues mailing list