-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Odd error when installing update-site zip #551
Comments
Can you be more specific what "installing update-site zips" refers to as one can't "install" a zip file or an update-site. If you refer to the ues of update-site-urls that point to a zip file, I strongly would discourage such usage, just simply expand the zip file for maximum compatibility, beside that using the latest Eclipse release will get you the best chance to profit from bugfixes and possibly analysis of problems. |
@laeubi , What I meant was choose a zip that's an update-site from the Add Repository panel from the Archive choice. Or something like "p2 Install Repository" from here https://jazz.net/downloads/workflow-management/releases/7.0.3?p=allDownloads if that's a more accessible example of the update-site zip on my local machine. Unfortunately, we're not in a possible to build our product against the latest release of Eclipse and use the one that's available every March. So, if there was a critical fix in newer release, we would port that to our Eclipse 4.31 base and apply it as a patch. |
Note that just a few weeks ago I made some improvements related to zipped update sites: eclipse-platform/eclipse.platform.ui#2265 I don't believe there is an actual problems with updating from a zipped update site because that whole process worked well for me while testing to ensure that a file:jar URL is preferred for an https: URL. I think all the problem you show are not related to updating from a zipped update site. In any case, it's impossible to fix something if we can't reproduce the problem. So it's unlikely anyone can take action on this report unless you provide a series of steps that we can follow that will reproduce a problem. 😞 |
I'm think I'm getting closer to isolating the issue... Thanks for your fix you mentioned, @merks , will work on getting that into our product ASAP. So, I rebuilt our product, stripped out all our in-house plugins and only keep Eclipse community stuff. Then tried to install the jazz.net Engineer Workflow Management update-site above (since it's free to download, just need a jazz.net account) and I get this screen... Which is very strange because I've applied the patch in relation to #512. So I'm not sure why all these packages are trying to update. As these are the only software sites available: Unless this is causing it - eclipse-m2e/m2e-core#1751 |
The m2e repository has many references: Those in turn could also have references... I think this system property can turn them off: p2/bundles/org.eclipse.equinox.p2.engine/src/org/eclipse/equinox/p2/engine/ProvisioningContext.java Lines 73 to 83 in ec65256
|
I'm developing an RCP application based on Eclipse 4.31 and Java 17. While the product builds, packages, and runs smoothly overall, I'm encountering an issue when installing update-site zips.
and
When attempting to install update-site zips, the process eventually triggers the "Restart Workbench" dialog as expected. However, upon confirming the restart, nothing happens. I have to manually close and relaunch the application. After restarting, the updates appear to have been successfully installed, but the restart mechanism itself seems unresponsive.
I thought it was related to this issue - #512, so I applied a patch to my product to incorporate the changes used to fix it. That did not make a difference.
Other things I've tried... In my Available Software Sites, I have the following:
I tried removing all of those update-sites, save for the file / zip I'm trying to install. No difference there. And for some reason WWD and other update-sites are being contacted. I do have WWD and other Eclipse Projects as part of my offering, but as you can see, those update-sites are not available or present in the Preferences. And the update-site I want to install does not contain any nested update-sites.
Interestingly enough, the only thing that did work is if "Contact all update sites..." is unchecked.
A lot of things are logged, so it's hard to tell what's really relevant, but the things that stick out to me are:
The text was updated successfully, but these errors were encountered: