Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Starting Eclipse Commandline With Equinox Launcher"

(→‎<b style="color:darkgreen">A</b>nt Script)
(→‎Ant Script)
(10 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
Launching Eclipse with the new Equinox jar is as easy as <b style="color:darkgreen">A</b>, <b style="color:orange">B</b>, <b style="color:darkred">C</b>.
 
Launching Eclipse with the new Equinox jar is as easy as <b style="color:darkgreen">A</b>, <b style="color:orange">B</b>, <b style="color:darkred">C</b>.
 +
 +
Note that the initial releases of Eclipse 3.3 on Windows have a configuration bug preventing the following approach from working. See [http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg03416.html this mail thread] for details.
  
 
=== <b style="color:darkgreen">A</b>nt Script ===
 
=== <b style="color:darkgreen">A</b>nt Script ===
  
−
  <nowiki><!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ --></nowiki>
+
<source lang="xml">
 +
  <!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ -->
 
   <property name="eclipse.home" value="."/>
 
   <property name="eclipse.home" value="."/>
 
   
 
   
Line 15: Line 18:
 
   <java classpath="''${eclipse.home}''/eclipse/plugins/org.eclipse.equinox.launcher.jar"
 
   <java classpath="''${eclipse.home}''/eclipse/plugins/org.eclipse.equinox.launcher.jar"
 
   .../>
 
   .../>
 +
</source>
  
 
Or, if you are using Ant 1.7 and don't like copying resources around (or don't have permission to do so) this appears to work to set the path to the newest available equinox launcher jar in a property for later use:
 
Or, if you are using Ant 1.7 and don't like copying resources around (or don't have permission to do so) this appears to work to set the path to the newest available equinox launcher jar in a property for later use:
  
−
  <nowiki><!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ --></nowiki>
+
<source lang="xml">
 +
  <!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ -->
 
   <property name="eclipse.home" value="."/>
 
   <property name="eclipse.home" value="."/>
 
   
 
   
−
   <nowiki><!-- store path to newest launcher JAR in path id 'newest.equinox.launcher.path.id' --></nowiki>
+
   <!-- store path to newest launcher JAR in path id 'newest.equinox.launcher.path.id' -->
 
   <path id="newest.equinox.launcher.path.id">
 
   <path id="newest.equinox.launcher.path.id">
 
     <first count="1">
 
     <first count="1">
Line 39: Line 44:
 
   </path>
 
   </path>
 
   
 
   
−
   <nowiki><!-- turn the path into a property --></nowiki>
+
   <!-- turn the path into a property -->
 
   <property name="equinox.launcher.jar.location" refid="newest.equinox.launcher.path.id" />
 
   <property name="equinox.launcher.jar.location" refid="newest.equinox.launcher.path.id" />
 
   
 
   
−
   <nowiki><!-- you can now reference the jar through the property ${equinox.launcher.jar.location} --></nowiki>
+
   <!-- you can now reference the jar through the property ${equinox.launcher.jar.location} -->
 
   <echo message="Using equinox launcher jar: ${equinox.launcher.jar.location}" />
 
   <echo message="Using equinox launcher jar: ${equinox.launcher.jar.location}" />
 +
</source>
  
 
=== <b style="color:orange">B</b>ash Shell Script ===
 
=== <b style="color:orange">B</b>ash Shell Script ===
Line 49: Line 55:
 
   #!/bin/bash
 
   #!/bin/bash
 
   
 
   
−
   # set path to eclipse folder. If local folder, use '.'; otherwise, use /path/to/eclipse/
+
   # set path to eclipse folder. If the same folder as this script, use the default; otherwise, use /path/to/eclipse/
−
   eclipsehome=".";
+
   eclipsehome=`dirname $BASH_SOURCE`;
 
   
 
   
 
   # get path to equinox jar inside $eclipsehome folder
 
   # get path to equinox jar inside $eclipsehome folder
−
   cp=$(find ''$eclipsehome'' -name "org.eclipse.equinox_*.jar" | sort | tail -1);
+
   cp=$(find ''$eclipsehome'' -name "org.eclipse.equinox.launcher_*.jar" | sort | tail -1);
 
   
 
   
 
   # start Eclipse w/ java
 
   # start Eclipse w/ java
Line 60: Line 66:
 
=== <b style="color:darkred">C</b>md/Bat Script ===
 
=== <b style="color:darkred">C</b>md/Bat Script ===
  
−
Save this as eclipse.cmd. This has been tested with Windows XP Home Edition only.  
+
Save this as eclipse.cmd. This has been tested with Windows XP Pro (SP2).
  
 
   @echo off
 
   @echo off
Line 68: Line 74:
 
    
 
    
 
   :: get path to equinox jar inside ECLIPSEHOME folder
 
   :: get path to equinox jar inside ECLIPSEHOME folder
−
   for /f "delims= tokens=1" %%c in ('dir %ECLIPSEHOME%\plugins /b /s org.eclipse.equinox_*.jar') do set EQUINOXJAR=%%c
+
   for /f "delims= tokens=1" %%c in ('dir /B /S /OD %ECLIPSEHOME%\plugins\org.eclipse.equinox.launcher_*.jar') do set EQUINOXJAR=%%c
 
    
 
    
 
   :: start Eclipse w/ java
 
   :: start Eclipse w/ java
 
   echo Using %EQUINOXJAR% to start up Eclipse...
 
   echo Using %EQUINOXJAR% to start up Eclipse...
−
   java -jar %EQUINOXJAR% org.eclipse.equinox.launcher.Main ...
+
   java -jar %EQUINOXJAR% ...
 +
 
 +
=== Variations ===
 +
 
 +
* If you're looking to run JUnit tests headlessly, see [[Starting_Eclipse_Commandline_With_Equinox_Launcher/Headless_JUnit_Testing|Headless JUnit Testing]].
 +
 
 +
* If you're looking to the Equinox p2 Admin UI, see [[Starting_Eclipse_Commandline_With_Equinox_Launcher/p2_Admin_UI|p2 Admin UI]].
 +
 
  
−
[[Category:Releng]] [[Category:Equinox]] [[Category:Java]]
+
[[Category:Releng]] [[Category:Equinox|Launcher]] [[Category:Java]]
 +
[[Category:Launcher]]

Revision as of 14:51, 30 October 2010

Launching Eclipse with the new Equinox jar is as easy as A, B, C.

Note that the initial releases of Eclipse 3.3 on Windows have a configuration bug preventing the following approach from working. See this mail thread for details.

Ant Script

  <!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ -->
  <property name="eclipse.home" value="."/>
 
  <nowiki><!--  get path to equinox jar inside ${eclipse.home} folder (copy/rename actual jar) --></nowiki>
  <copy tofile="''${eclipse.home}''/eclipse/plugins/org.eclipse.equinox.launcher.jar">
    <fileset dir="''${eclipse.home}''/eclipse/plugins"
      includes="**/org.eclipse.equinox.launcher_*.jar"/>
  </copy>
 
  <nowiki><!-- start Eclipse w/ java --></nowiki>
  <java classpath="''${eclipse.home}''/eclipse/plugins/org.eclipse.equinox.launcher.jar"
  .../>

Or, if you are using Ant 1.7 and don't like copying resources around (or don't have permission to do so) this appears to work to set the path to the newest available equinox launcher jar in a property for later use: 

  <!-- set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse or /path/to/eclipse/ -->
  <property name="eclipse.home" value="."/>
 
  <!-- store path to newest launcher JAR in path id 'newest.equinox.launcher.path.id' -->
  <path id="newest.equinox.launcher.path.id">
    <first count="1">
      <sort>
        <fileset dir="${eclipse.home}/eclipse/plugins" includes="**/org.eclipse.equinox.launcher_*.jar"/>
 
        <nowiki><!-- Seems the default order is oldest > newest so we must reverse it.
            The 'reverse' and 'date' comparators are in the internal antlib
            org.apache.tools.ant.types.resources.comparators.
         --></nowiki>
        <reverse xmlns="antlib:org.apache.tools.ant.types.resources.comparators">
          <nowiki><!-- 'date' inherits 'reverse's namespace --></nowiki>
          <date/>
        </reverse>
      </sort>
    </first>
  </path>
 
  <!-- turn the path into a property -->
  <property name="equinox.launcher.jar.location" refid="newest.equinox.launcher.path.id" />
 
  <!-- you can now reference the jar through the property ${equinox.launcher.jar.location} -->
  <echo message="Using equinox launcher jar: ${equinox.launcher.jar.location}" />

Bash Shell Script

 #!/bin/bash

 # set path to eclipse folder. If the same folder as this script, use the default; otherwise, use /path/to/eclipse/
 eclipsehome=`dirname $BASH_SOURCE`;

 # get path to equinox jar inside $eclipsehome folder
 cp=$(find $eclipsehome -name "org.eclipse.equinox.launcher_*.jar" | sort | tail -1);

 # start Eclipse w/ java
 /opt/java50/bin/java -cp $cp org.eclipse.equinox.launcher.Main ...

Cmd/Bat Script

Save this as eclipse.cmd. This has been tested with Windows XP Pro (SP2). 

 @echo off

 :: set path to eclipse folder. If local folder, use '.'; otherwise, use c:\path\to\eclipse
 set ECLIPSEHOME=.
 
 :: get path to equinox jar inside ECLIPSEHOME folder
 for /f "delims= tokens=1" %%c in ('dir /B /S /OD %ECLIPSEHOME%\plugins\org.eclipse.equinox.launcher_*.jar') do set EQUINOXJAR=%%c
 
 :: start Eclipse w/ java
 echo Using %EQUINOXJAR% to start up Eclipse...
 java -jar %EQUINOXJAR% ...

Variations

  • If you're looking to the Equinox p2 Admin UI, see p2 Admin UI.
Retrieved from "https://wiki.eclipse.org/index.php?title=Starting_Eclipse_Commandline_With_Equinox_Launcher&oldid=225552"

Back to the top