[jbosstools-issues] [JBoss JIRA] (JBDS-2263) JBDS 6 fails to open Software/Update tab in JBoss Central

Nick Boldt (JIRA) jira-events at lists.jboss.org
Fri Sep 7 12:01:33 EDT 2012


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

Nick Boldt commented on JBDS-2263:
----------------------------------

I've created https://devstudio.jboss.com/updates/6.0-staging/central/core/ and the rest of the forthcoming URLs on devstudio.jboss.com/updates/6.0*.

However, since the correct URL is 6.0-staging, not 6.0/staging (JBDS-2231) I've also updated the plugin in the 4.0.0.Alpha1 branch so that this will be fixed in this weekend's respin.
                
> JBDS 6 fails to open Software/Update tab in JBoss Central
> ---------------------------------------------------------
>
>                 Key: JBDS-2263
>                 URL: https://issues.jboss.org/browse/JBDS-2263
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: central
>    Affects Versions: 6.0.0.Alpha1
>            Reporter: Stefan Bunciak
>            Assignee: Snjezana Peco
>            Priority: Blocker
>             Fix For: 6.0.0.Alpha2
>
>
> {code}
> org.eclipse.core.runtime.CoreException: IO failure: cannot load discovery directory
> 	at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:122)
> 	at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
> 	at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1509)
> 	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: java.io.FileNotFoundException: https://devstudio.jboss.com/updates/6.0/staging/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:474)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:431)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273)
> 	at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.stream(P2TransportService.java:93)
> 	at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.stream(WebUtil.java:161)
> 	at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.readResource(WebUtil.java:95)
> 	at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:107)
> 	... 3 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list