Welcome to the Jazz Community Forum
silent/scripted install eclipse patch/plugin help
can anyone point me to process/best practice on how to install a patch or new plugin into an eclipse client via some silent/scripted install process.
the client(s) were installed/setup in lots of different ways (unfortunately) and not all (many!) are recorded in any reqistry or ...
I can find the location of the file we need to change (and the extra plugins it needs) on the filesystem
and can use that for input to the script..
Sam
the client(s) were installed/setup in lots of different ways (unfortunately) and not all (many!) are recorded in any reqistry or ...
I can find the location of the file we need to change (and the extra plugins it needs) on the filesystem
and can use that for input to the script..
Sam
4 answers
Possibly the longest reply (in terms of time) yet, but this is what I've come up with. In my case, I have the eclipse RTC 4.0.3 client, which is Eclipse 3.6 (Helios) based and I thought that others may benefit.
I've used the p2 director to perform the provisioning operations.
I've added the Eclipse Market Place plugins (that IBM usual strips out of it's installs!), then I add MercurialEclipse, then EGit, then Subclipse, then the M2E plugin and then follow up with the internally discovered Maven SCM Handler for Subclipse. The Maven SCM Handler for EGit requires a minimum of EGit 3, which does not work on Eclipse 3.6.
I hope this is of benefit to others. Hopefully this would have worked for you.
So we have:
#!/bin/bash # Author: Chris Graham - ChrisGWarp@gmail.com # Installs: Additional plugins/features into IBM Rational RTC Eclipse (3.6) Client Linux : 4.0.3 cd /opt/IBM/TeamConcert # # If you run into trouble, try: #./eclipse -application org.eclipse.equinox.p2.director -nosplash -list -repository http://download.eclipse.org/mpc/helios #./eclipse -application org.eclipse.equinox.p2.director -nosplash -list -repository http://mercurialeclipse.eclipselabs.org.codespot.com/hg.wiki/update_site/stable/ #./eclipse -application org.eclipse.equinox.p2.director -nosplash -list -repository http://download.eclipse.org/egit/updates-2.1 #./eclipse -application org.eclipse.equinox.p2.director -nosplash -list -repository http://subclipse.tigris.org/update_1.8.x #./eclipse -application org.eclipse.equinox.p2.director -nosplash -list -repository http://download.eclipse.org/technology/m2e/releases # Install: Eclipse Market Place (for Helios/3.6) ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://download.eclipse.org/mpc/helios,http://download.eclipse.org/releases/helios,http://download.eclipse.org/releases/kepler -installIU org.eclipse.epp.mpc.feature.group/1.0.1.v20100826-2143 # Install: Mercurial Eclipse ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://mercurialeclipse.eclipselabs.org.codespot.com/hg.wiki/update_site/stable/ -installIU mercurialeclipse.feature.group/2.1.0.201304290948 # Install: EGit 2.1 ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://download.eclipse.org/egit/updates-2.1 -installIU org.eclipse.egit.feature.group/2.1.0.201209190230-r # Install: Subclipse (Note: RTC already installs a version of tmate's svnkit, so not needed here). # Specify specific versions #./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://subclipse.tigris.org/update_1.8.x -installIUs com.collabnet.subversion.merge.feature.feature.group/3.0.13,net.java.dev.jna.feature.group/3.4.0.t20120117_1605,org.tigris.subversion.clientadapter.feature.feature.group/1.8.6,org.tigris.subversion.clientadapter.javahl.feature.feature.group/1.7.10,org.tigris.subversion.clientadapter.svnkit.feature.feature.group/1.7.9.2,org.tigris.subversion.subclipse.feature.group/1.8.22,org.tigris.subversion.subclipse.graph.feature.feature.group/1.1.1 # Or accept the latest (by default) ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://subclipse.tigris.org/update_1.8.x -installIUs com.collabnet.subversion.merge.feature.feature.group,net.java.dev.jna.feature.group,org.tigris.subversion.clientadapter.feature.feature.group,org.tigris.subversion.clientadapter.javahl.feature.feature.group,org.tigris.subversion.clientadapter.svnkit.feature.feature.group,org.tigris.subversion.subclipse.feature.group,org.tigris.subversion.subclipse.graph.feature.feature.group # Install: M2E 1.4.1 ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://download.eclipse.org/technology/m2e/releases,http://download.eclipse.org/releases/helios,http://download.eclipse.org/releases/kepler -installIUs org.eclipse.m2e.feature.feature.group/1.4.1.20140328-1905,org.eclipse.m2e.sdk.feature.feature.group/1.4.1.20140328-1905,org.eclipse.m2e.site/1.4.1.20140328-1905,org.eclipse.m2e.logback.feature.feature.group/1.4.1.20140328-1905,org.eclipse.m2e.scm/1.4.1.20140328-1905 # Install: Maven SCM Handler for Subclipse ./eclipse -application org.eclipse.equinox.p2.director -nosplash -repository http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-subclipse/0.13.0/N/0.13.0.201303011221/ -installIU org.sonatype.m2e.subclipse.feature.feature.group/0.13.0.201303011221 # Note: The Maven SCM Handler for EGit can not be installed, as it requires EGit 3.0+ and 2.1 is the latest we can install.
well, the 'cheap' way is to copy the files into the plugins and features folder
and add -clean to the eclipse.ini as the first line
| Well, not so fast.. this causes Eclipse to clean start every time, not just once (the ini is not cleaned up)
and add -clean to the eclipse.ini as the first line
| Well, not so fast.. this causes Eclipse to clean start every time, not just once (the ini is not cleaned up)
Comments
your can remove -clean options after running the options once...
maybe, but I have 5000 clients to do this on all occurrences of eclipse that have a specific jar file in plugins folder. I don't know when the user will start that eclipse
and I have no way of fixing just that one
I need a totally unattended approach..
I also can't install tools on their system (like Installation manager), as there is no way to know how they installed the eclipse setup in question..
on my system I have 5 instances, 3 with the jar file in question.. One IM install,
one unzip, and one built with the WTP unzip and the rtc p2 installed manually.
all three need to be modified
Hi Sam,
if your RTC eclipse client was installed using IBM installation manager you can use the silent installation instruction to apply upgrade (patch).
if generic standalone eclipse your can add the plugins from the dropins directory which is on the same level as the configuration directory where you have the eclipse.exe and eclipse.ini files.
if your RTC eclipse client was installed using IBM installation manager you can use the silent installation instruction to apply upgrade (patch).
if generic standalone eclipse your can add the plugins from the dropins directory which is on the same level as the configuration directory where you have the eclipse.exe and eclipse.ini files.
Comments
thx,
on the client I wanted to try this, there was not a dropins directory. I created one, put the jar files there, but they were not used on the next startup.
this was a standalone eclipse wtp unzip install, with the RTC P2 installed on top.
You will probably want to create proper p2 metadata for your changes and install them using the p2 director. You will probably find better guidance for this by asking in the eclipse p2 forum.
Hi Sam,
If you are using jar files, it will be dropins/plugins/ directory.