Eclipse Oomph: Suppress Welcome Page

I am frequently spawning Eclipse workspaces with Oomph setups and the first action I do when a new workspace is provisioned is to close Eclipse’s welcome page. So I wanted to suppress that for a current project setup. So I started searching where Eclipse stores the preference that disables the intro page. The location of that preference is within the workspace directory at

.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs

The content of the preference file is

eclipse.preferences.version=1
showIntro=false

So to make Oomph create the preference file before the workspace is started the first time use a Resource Creation task and set the Target URL

${workspace.location|uri}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs

Then put the above mentioned preference content as Content value.

4 thoughts on “Eclipse Oomph: Suppress Welcome Page

  1. Hi Karsten,

    I meanwhile learned that $workspace.location is undefined if you try to setup an oomph based installation without selecting any product, leading to wizard asking you for that variable repeatedly. You can workaround this either by using osgi.instance.area as described by Eike at https://www.eclipse.org/forums/index.php/t/1103362/, or you simply replace the $workspace.location variable by $install.location and add “/ws” to the path part after the variable (assuming you use the nested workspace directory schema).

    • Thanks for this interesting addition! I’m not sure if it is safer to assume the workspace location based on the installation location. IMO the possibility to use a setup without a product is less likely. I’ve never done that so far honestly.
      But IF you have that situation then this would be an important thing to consider.

  2. Can you show an example for both suggestions?
    How would using osgi.instance.area help?

    What does this mean:
    “or you simply replace the $workspace.location variable by $install.location and add “/ws” to the path part after the variable (assuming you use the nested workspace directory schema).”

    That would be
    ${install.location|uri}/ws/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs

    This assumes that ${install.location|uri}/ws is my workspace, right? That would mean that I need to know the workspace location before creating the installer?

  3. > That would mean that I need to know the workspace location before creating the installer?

    Yes, ${install.location|uri}/ws would assume that the workspace is located below the install directory. ${workspace.location|uri} would actually be the workspace directory, but as Michael points out, this could be a problem when no product is selected. But that is not my use case, so for me the described approach works.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s