Bugzilla – Full Text Bug Listing
| Summary: | [rum] standaloneUpdate fails with 3.4M6 on build.eclipse.org | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Martin Oberhuber <mober.at+eclipse> | ||||
| Component: | p2 | Assignee: | DJ Houghton <dj.houghton> | ||||
| Status: | VERIFIED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, david_williams, john.arthorne, kim.moir, mark.melvin, mary, mknauer, pascal, philippe_mulet, rcleveng, richard.gronback, Sergey.Armensky, ted, vivkong | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.4 | ||||||
| Hardware: | Power PC | ||||||
| OS: | Linux-GTK | ||||||
| URL: | http://download.eclipse.org/eclipse/downloads/drops/S-3.4M6-200803301350/ | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Martin Oberhuber
Note: I did not try using the dropins/ folder for the CDT download because what I have here is a compressed update site, and the P2 Getting Started Wiki: http://wiki.eclipse.org/Equinox_p2_Getting_Started#Dropins talks about possibility to drop plugins, features, extension locations or installations but it does NOT talk about possibility to drop in update sites or compressed update sites (where the features are not expanded but in Jars, and potentially also some plugins need to be unpacked). Here is an automatic removal script that saved the day for me: It gets rid of P2 as per the Wiki, and finally made the standaloneUpdate work: # Remove P2 due to https://bugs.eclipse.org/bugs/show_bug.cgi?id=225537 # See http://wiki.eclipse.org/Equinox_p2_Removal rm -rf eclipse/configuration/* eclipse/configuration/.settings cp ../eclipse-3.3-linux-gtk-ppc/eclipse/configuration/config.ini eclipse/configuration cp -f ../eclipse-3.3-linux-gtk-ppc/eclipse/eclipse.ini eclipse/ rm -rf eclipse/features/org.eclipse.equinox.p2.user.ui* rm -f eclipse/plugins/org.eclipse.equinox.p2.* rm -rf eclipse/p2 # </Remove P2> Created attachment 94882 [details] Plugin providing command line app Martin, the work on full interop with update manager and p2 is not complete yet and you are being hit by this. Going forward I would recommend you to replace the invocation of the um commands by the following p2 command line operation <line return just here for clarity>: -application org.eclipse.equinox.p2.director.app.application -metadataRepository file:d:/tmp/cdt/site.xml -artifactRepository file:d:/tmp/cdt/site.xml -installIU org.eclipse.cdt.feature.group Note that the parameter to the installIU is the featureId suffixed by "feature.group" (e.g. in this case the CDT feature id was org.eclipse.cdt.feature). I attach here the plug-in providing the command line application because it is not yet part of the SDK (bug 225778). Thanks Pascal. I appreciate the extra plugin as well as instructions how to use it. But this doesn't help me coming up with a script to automatically install from the update site, in a form that only uses CVS-tagged repository artifacts (for the build being reproducable). IMHO a sensible workaround needs to come up with instructions that only involve artifacts which will remain intact in the future and allow a reproducable build. Such as the already promised un-p2ized downloadable eclipse SDK for instance. Until such a workaround is available the bug is still a major regression for me, because it keeps me from doing what I need to do in a sensible manner. OK I could download eclipse-platform-3.3 for the sole purpose of getting its eclipse.ini and config.ini files but that's not a very nice solution, is it? I'm sorry but I'm not sure I understand what you mean by:
> But this doesn't help me coming up with a script to automatically install
from the update site, in a form that only uses CVS-tagged repository artifacts
(for the build being reproducable).
Could you please give me more details here, or maybe directly call me (and then I could summarize the discussion here).
Long Story short, I want this to happen: http://wiki.eclipse.org/Equinox_p2_Getting_Started#Removing_p2 "In addition, to help smooth the transition for adopters, the platform 3.4 M6 build will have a copy available with p2 removed for you." Making my automated script to build RSE much simpler and work the same way it's been working since Eclipse 3.2 (no more regression, not for me nor for others). We decided instead to provide a script that will remove p2 from any 3.4 build. This is now available on the Eclipse project download page from 3.4 M6 onwards (see link on right hand side of the page). Work covering the synchronization between the platform.xml and p2's bundles.info file is covered by bug 224482. The script for removing p2 from a build is attached to bug 224908. From reading Martin's comments, it sounds like he wants a non-p2 version of the SDK so I will mark this bug as a duplicate. If there is something else that you are looking for, please re-open. *** This bug has been marked as a duplicate of bug 224908 *** Martin, we've made a lot of progress in handling compatibility with standalone update, so if you are still using these scripts it would be good feedback to know if this is working for you in M7 candidate builds. You should be able to use legacy standalone update and p2 will synchronize automatically on the next startup of the target. Of course, moving to p2 tools is still a better long term answer because it will enable you to take advantage of p2 capabilities not available in UM. Verified old commandline update manager app works in I20080502-0100 (3.4M7) |