Eclipse Community Forums: Oomph » How to import plugins from other installation?

Home » Eclipse Projects » Oomph » How to import plugins from other installation?

How to import plugins from other installation? [message #1799949]

Mon, 17 December 2018 15:14

Eclipse User

I used to "copy" installed plugins using File/Import /Install/FromExistingInstallation. feature. It was nice because I didn't had to remember every plugin every time I upgrade.

But since I started to use oomph to install my IDE I can't do this any more. At least I can't do what I used todo. When I go to import and select the other installation folder an error message appears: "specify the path to a valid application installation".

Is there a easy way to copy plugins that I've installed in other installations?

thanks

[Updated on: Mon, 17 December 2018 15:15] by Moderator

Re: How to import plugins from other installation? [message #1799960 is a reply to message #1799949]

Tue, 18 December 2018 00:23

Eclipse User

An Oomph-based installation by default will use a shared bundle pool so the bundles will not actually be physically nested in the installation but rather are shared between installations.

When I want something installed in every IDE, I use a p2 task in my user.setup (Navigate -> Open Setup -> User). E.g., I have viPlugin installed in every IDE I install because I have the following in my user.setup.

<?xml version="1.0" encoding="UTF-8"?>
<setup.p2:P2Task
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
    label="VI">
  <requirement
      name="com.mbartl.viplugin.eclipse.feature.group"
      optional="true"/>
  <repository
      url="http://viplugin.com"/>
</setup.p2:P2Task>

There are tools already available that make it easy to create a p2 task:

https://wiki.eclipse.org/Eclipse_Oomph_Authoring#How_to_install_Eclipse_plugins_using_the_P2_Director_and_Repository_Explorer

Many people use Oomph to author specialized product setups that install a combination of features. More commonly people author project setups that not only provision an installation, but also a workspace with the actual projects on which they work.

E.g., for EMF I have these simple instructions for creating a development environment for working on EMF:

https://ci.eclipse.org/emf/

This project setup ensures that the tools needed to work on EMF's source code are installed, it clones the EMF Git repository, provisions the target platform with the bundles needed to compile EMF, imports EMF's projects into the workspace, and organizes those projects into working sets, and so on.

In other words, Oomph has all the infrastructure you need to automate creating specialized installations and specialized workspaces.

Previous Topic:	Outline view blank when using Oomph setup editor
Next Topic:	Purpose of branding info

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 08:30:13 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter