Eclipse Community Forums: Oomph » Getting started with Oomph

Home » Eclipse Projects » Oomph » Getting started with Oomph

Getting started with Oomph [message #1767866]

Tue, 11 July 2017 13:37

Eclipse User

I currently use a p2f file to install required features and a psf file to clone repos and import projects. I am investigating if I can switch to an oomph setup and have a couple of questions. I tried to find answers in the existing docs but was not successful.

1. Does it matter where the setup file is stored? The overall project is in 5 git repos that all need to be cloned and projects need to be imported from them.
2. I was able to use a task to clone a git repo. How do I import the projects? There seems to be a project import task but elsewhere I found the recommendation to use a target task (by the way, what IS a targlet?)
3. Assume someone has already installed eclipse from a zip file. How can a setup be added to this existing installation?
4. Assume I add a new plugin project or a new git repo to my project. I assume that I need to update the setup accordingly, but what happens now? How is this change propagated to other developers such that the new project shows up in their workspaces?
5. What is the best way to find out which tasks are available and what they actually do? I'm trying to avoid reading the source code.

Thanks.

Re: Getting started with Oomph [message #1768032 is a reply to message #1767866]

Thu, 13 July 2017 02:56

Eclipse User

1. Not really, but ideally they're located at some raw text http location so you can point at the latest version without copying it to your machine.
2. There are several tasks to import projects. The obvious is Import Projects task. The Targlet task will also import projects; the task is also user for defining the contents of PDE's target platform. You can point the targlets at p2 udpate sites and at local folders in your git clone (source locators), and it will resolve all dependencies of those projects but additional things you might want. Note you can look at all the existing project setups using Navigate -> Open Setup -> Parent Models -> Catalog Index Eclipse to open the main index and from there you can see all other product and project catalogs. Also note that if you create a new setup in a project that is in a git clone, the template will create much of the basic tasks that you'll need/want.
3. File -> Import -> Oomph -> Projects into Workspace
4. Ideally you use an http location that is a view of the setup maintained in git. (And ideally you have Redirection task that redirects to the local in the local git clone, so you can edit it locally, and test it before committing it.). Then new uses will always see the latest version and existing installations will see the latest version when they do a pull.
5. Other than the wiki https://wiki.eclipse.org/Eclipse_Oomph_Authoring there isn't so documentation. But using the wizards you should have a good starting point and the names of the tasks are fairly clear on the general intent. And you can look at how all the other projects at Eclipse and many on Github have defined there setups using these tasks.

Re: Getting started with Oomph [message #1768416 is a reply to message #1768032]

Tue, 18 July 2017 09:23

Eclipse User

Quote:

And ideally you have Redirection task that redirects to the local in the local git clone, so you can edit it locally, and test it before committing it.

What does this redirect look like?
Is it something like this in eclipse.ini:
-Doomph.redirect.<my setup id>=<raw http location>-><local copy on disk>
Would this try the http location if there is no local copy of the setup file?

Re: Getting started with Oomph [message #1768425 is a reply to message #1768416]

Tue, 18 July 2017 10:05

Eclipse User

Sorry, I misdirected with mention of a Redirection task... You could have such a task as this:

<?xml version="1.0" encoding="UTF-8"?>
<setup:EclipseIniTask
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
    option="-Doomph.redirection.emf.setup"
    value="=http://git.eclipse.org/c/emf/org.eclipse.emf.git/plain/releng/org.eclipse.emf.releng/EMF.setup->${emf.git.clone.location|uri}/releng/org.eclipse.emf.releng/EMF.setup"
    vm="true"/>

and yes, when this is processed, the code checks that are resource at target URI actually exists. So in this case, when the clone doesn't exist yet, the remote version is used. Once the clone task creates the clone, subsequent performs will use the version in the clone itself.

Previous Topic:	Project import task does not import the newly created projects on Eclipse startup
Next Topic:	Install feature on demand?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 08 11:23:13 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter