|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: index:/org.eclipse.setup fails to resolve with 2021-03 [message #1854236 is a reply to message #1840870] |
Mon, 08 August 2022 17:31   |
 Elie Richa
Messages: 72
Registered: February 2016 |
Member |
|
|
Hello Ed,
I'm encountering this same issue again with a fresh install of Eclipse Modeling Tools 2021-03 using Oomph. When the installation completes, the new instance is unable to load Oomph setups when "Perform Setup Tasks" is invoked or any of the setups are navigated.
As before, the error is about the "archive:" protocol. This occurs at least on macOS and Linux (Ubuntu 20.04).
I imagine this is fixed in newer versions, but assuming I wanted to stay on 2021-03, what would the solution be here?
Many thanks,
eclipse.buildId=4.19.0.I20210303-1800
java.version=11.0.16
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.modeling.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.modeling.product
org.eclipse.oomph.setup.ui
Error
Mon Aug 08 08:52:14 PDT 2022
org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$ResourceLocator.demandLoadHelper(ResourceSetImpl.java:804)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$MappedResourceLocator.getResource(ResourceSetImpl.java:1204)
at org.eclipse.oomph.setup.internal.core.util.SetupCoreUtil$3.getResource(SetupCoreUtil.java:466)
...
Caused by: org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createIOException(ECFURIHandlerImpl.java:555)
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.access$15(ECFURIHandlerImpl.java:542)
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ConnectionHandler.process(ECFURIHandlerImpl.java:1805)
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createInputStream(ECFURIHandlerImpl.java:323)
at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:358)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1314)
at org.eclipse.oomph.setup.internal.core.util.ResourceMirror$LoadJob.perform(ResourceMirror.java:232)
at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:434)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.net.MalformedURLException: unknown protocol: archive
at java.base/java.net.URL.<init>(URL.java:652)
at java.base/java.net.URL.fromURI(URL.java:719)
at java.base/java.net.URI.toURL(URI.java:1116)
at org.eclipse.ecf.provider.filetransfer.identity.FileTransferID.getURL(FileTransferID.java:80)
at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879)
at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:578)
at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:108)
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$InputStreamConnectionHandler.sendConnectionRequest(ECFURIHandlerImpl.java:1950)
at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ConnectionHandler.process(ECFURIHandlerImpl.java:1649)
... 6 more
Elie Richa, Ph.D
Software Engineer, AdaCore
https://www.adacore.com
|
|
|
|
| Re: index:/org.eclipse.setup fails to resolve with 2021-03 [message #1854257 is a reply to message #1854245] |
Tue, 09 August 2022 11:21 |
Elie Richa
Messages: 72
Registered: February 2016 |
Member |
|
|
Hmm there are things I don't understand. Apologies if these are obvious questions.
The releases/2021-03 repository contains org.eclipse.emf.cdo.common [4.13.0.v20210308-1749] and org.eclipse.oomph.setup.core [1.19.0.v20210221-1019].
There were two patches addressing this issue, one in CDO and one in Oomph. Both fixes happened after the dates in the above build qualifiers of course.
So do I understand correctly that the fixes never made it into the releases/2021-03 repository? Which means that installing from releases/2021-03 should create that issue systematically for everyone, not just me?
You mentioned installing a newer version of CDO. Do you mean I should install CDO from the releases/2021-06 repository for example?
I did that using the traditional "Install New Software" wizard. It was CDO 4.14.0 and it managed to install with no conflicts or earthquakes. After that my Eclipse instance was able to resolve Oomph setups. Then when running the tasks, I expected Oomph to downgrade CDO back to 4.13.0 because that's the version the the P2 Director task sees. But to my surprise Oomph did not do a downgrade. How come?
And finally, I wanted to find a way to propagate the solution to my team. So I tried adding a P2 Director task in our project setup to install CDO 4.14.0. I disabled merge so that the releases/2021-06 repository does not get used for resolving the main Eclipse Modeling Tools P2 Directory task.
<?xml version="1.0" encoding="UTF-8"?>
<setup.p2:P2Task
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
label="CDO"
mergeDisabled="true">
<requirement
name="org.eclipse.emf.cdo.epp.feature.group"
versionRange="[4.14.0,5.0.0)"/>
<repository
url="http://download.eclipse.org/releases/2021-06"/>
</setup.p2:P2Task>
The installation finished successfully but the result was a weird inconsistent installation where the Installation Details view only showed the CDO 4.14.0 feature (and none of the other features), but the actual cdo.common plugin was 4.13.0 and caused the same URI handler issue.
So is there something else I could try to propagate a solution through the Oomph project setup?
Many thanks,
Elie Richa, Ph.D
Software Engineer, AdaCore
https://www.adacore.com
|
|
|
| Re: index:/org.eclipse.setup fails to resolve with 2021-03 [message #1854262 is a reply to message #1854257] |
Tue, 09 August 2022 15:17 |
Ed Merks
Messages: 33145
Registered: July 2009 |
Senior Member |
|
|
Yes, many things going on. The installer generally includes https://download.eclipse.org/oomph/updates/milestone/latest (or https://download.eclipse.org/oomph/updates/latest for the nightly installer). Until 2022-03, the latest version of Oomph could be installed in very old IDEs, but the platform's changes for PGP signing could not be accommodated in a backward compatible way, so that stopped being true. So for older IDEs, the latest Oomph won't install but instead the Oomph version from the train gets installer, which can be quite old.
The generated product catalog includes version ranges on only a few of the features, and even for those, only sets the lower bound so you can always update the features of an installation. You should instead use a CDO site with mostly only CDO plugins, e.g.,
https://download.eclipse.org/modeling/emf/cdo/drops/R20220608-1105/
This for browser all the folders for CDO:
https://download.eclipse.org/justj/?file=modeling/emf/cdo/drops/R20220608-1105
I think just adding this site will install the latest CDO from that site while installing the rest as normal.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
Powered by
FUDForum. Page generated in 5.06089 seconds
] 
Search
Help
Register
Login
Home
