Community
Participate
Working Groups
Steps to reproduce: tar -zxvf egit.tgz tar -zxf eclipse-platform-3.7-linux-gtk-x86_64.tar.gz mv eclipse eclipse-platform mkdir workspace #Install a dropin into cascaded config, and verify it has worked. mkdir -p cascaded-config/dropins echo "path=`pwd`/1.1.0" > cascaded-config/dropins/egit.link # Verify that the drop-in has worked # "Git Repository Exploring" perspective should be there: ./eclipse-platform/eclipse -install eclipse-platform/ -configuration `pwd`/cascaded-config/config -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area=`pwd`/eclipse-platform/configuration -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true -data workspace # Install the error log view in eclipse-platform: cd eclipse-platform ./eclipse -application org.eclipse.equinox.p2.director -consolelog -nosplash \ -repository http://download.eclipse.org/eclipse/updates/3.7 \ -installIU org.eclipse.ui.views.log cd .. # Re-run eclipse, egit has disappeared! ./eclipse-platform/eclipse -install eclipse-platform/ -configuration `pwd`/cascaded-config/config -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area=`pwd`/eclipse-platform/configuration -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true -data workspace # Note there are no errors in the error log (other than unable to instantiate the Git Repo Exploring perspective). # Destroy the cascaded config and restart: rm -r cascaded-config mkdir -p cascaded-config/dropins echo "path=`pwd`/1.1.0" > cascaded-config/dropins/egit.link ./eclipse-platform/eclipse -install eclipse-platform/ -configuration `pwd`/cascaded-config/config -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area=`pwd`/eclipse-platform/configuration -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true -debug p2.options > p2.trace Having done this, trying to install egit from the central update site (using cascading configs as above also fails), point p2 at: http://download.eclipse.org/egit/updates And the installation appears to silently fail.
Doesn't seem to require dropins. Simple steps to reproduce: tar -zxf eclipse-platform-3.7-linux-gtk-x86_64.tar.gz mv eclipse eclipse-platform mkdir workspace #Install a dropin into cascaded config, and verify it has worked. mkdir -p cascaded-config/dropins # Install the error log view in eclipse-platform: cd eclipse-platform ./eclipse -application org.eclipse.equinox.p2.director -consolelog -nosplash \ -repository http://download.eclipse.org/eclipse/updates/3.7 \ -installIU org.eclipse.ui.views.log cd .. # Run eclipse with a cascaded configuration ./eclipse-platform/eclipse -install eclipse-platform/ \ -configuration `pwd`/cascaded-config/config -Dosgi.checkConfiguration=true \ -Dosgi.sharedConfiguration.area=`pwd`/eclipse-platform/configuration \ -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true \ -data workspace Help > Install New Software Point at: http://download.eclipse.org/egit/updates And choose Eclipse Egit and Eclipse Jgit. Restart Plugins aren't present in the IDE, though they can be seen under: Help > About Eclipse Platform > Installation Details > Installed Software shows them as installed. && cascaded-config/plugins/org.eclipse... but not under the Plugins or Configuration tab. Note if you don't install org.eclipse.ui.views.log first, then everything works... Note there aren't any obvious errors in the error log.
The platform release I'm using is just the one from here: http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/index.php
James, I will try your steps but one thing I wanted to mention is there is a "bug" where if you specify vm args on the command line then it won't use the ones in the eclipse.ini file. Also I noticed that your command-line didn't contain -vmargs so maybe that is needed too? I would recommend putting all the args in the eclipse.ini and then trying it. (which is what I will do as well)
Thanks DJ that's interesting to know. As it happens the steps work fine if I don't install the error log plugin - egit is installed into the plugins directory of the cascaded config dir. What's also interesting is that I've always installed a feature into a platform releases and use that as the base of my multi user shared installs. All worked fine until I attempted to install the error log plugin in this way. I wonder if there's an issue installing a plugin by name vs installing features?
Oops, I should have searched because it appears that bug was fixed in 3.7 (bug 323533). But the script should probably also have the missing -vmargs command. Adding Pascal to the CC in case he has insight about installing bundles directly.
*** This bug has been marked as a duplicate of bug 304132 ***
