Getting the Eclipse Build ID

Eclipse Bugzilla ask you for your Eclipse Build ID. As I learned from Paul Webster in Bug 300260 you can use the following to put this build ID into the clipboard:

CTRL+3 cbi (Copy Build Id)

Seems like Eclipse has a command for everything. :-)

About Lars Vogel

Lars Vogel is the founder and CEO of the vogella GmbH and works as Eclipse and Android consultant, trainer and book author. He is a regular speaker at international conferences, He is the primary author of vogella.com. With more than one million visitors per month this website is one of the central sources for Java, Eclipse and Android programming information.
This entry was posted in Eclipse. Bookmark the permalink.

3 Responses to Getting the Eclipse Build ID

  1. Ian Bull says:

    I20100119-0800

    wow, look at that. you’re right.

  2. david song says:

    Hi Vogel, thank you for your great web with Rich Editorial Content, it is very helpful for me.
    But I met a difficulty in obfuscate my rcp project these days and I googled but no good ideas. I use Obfuscate4e with proguard 4.3 or 4.4. errors always arose. I am puzzled by the exception. would you please give me a help or write a tutorial on your web? The exception log in my rcp is as below:
    !SESSION 2010-01-28 10:16:34.372 ———————————————–
    eclipse.buildId=unknown
    java.version=1.6.0_17
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN
    Command-line arguments: -os win32 -ws win32 -arch x86

    !ENTRY org.eclipse.osgi 4 0 2010-01-28 10:16:35.542
    !MESSAGE Application error
    !STACK 1
    java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType
    at com.micromms.b.a.k.(Unknown Source)
    at com.micromms.b.a.l.(Unknown Source)
    at com.micromms.fms.session.b.(Unknown Source)
    at com.micromms.fms.session.b.a(Unknown Source)
    at com.micromms.fms.Application.start(Unknown Source)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

  3. Lars Vogel says:

    @david can you please use the appropriated Eclipse forum for issuing your question? Please see http://www.vogella.de/faq.html#support

Comments are closed.