Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Generate .setup from an existing project
Generate .setup from an existing project [message #1783377] Mon, 12 March 2018 13:40 Go to next message
Wa Liu is currently offline Wa LiuFriend
Messages: 3
Registered: March 2018
Junior Member
Hi!

We have an existing project, everything is set up. Now we want to use oomph for installation and provisioning.
We want to create a product .setup (for the eclipse installation) and also a project .setup for all the settings in the workspace, including project import, git connection and so on.

Can we generate the 2 .setups from the existing eclipse installation and project workspace?

Why we're asking: over the time, we've added some eclipse plugins. When new developers join the team, they just copy the workspace folder from someone and have the same plugins. Now, with oomph, if we are to create the .setup from scratch, we would have to evaluate which plugins are already installed (in the old workspace) and select them for installing (in the new Product Model .setup).

I can imagine that other teams have also configured oomph for old projects, how was this done? The same question for the imported projects - eclipse should be able to generate a .setup which imports all projects from the right location.

What we tried: eclipse -> Navigate -> Open Setup -> Self Products / Installation / Workspace. This gives us a .setup model. Our expectation was than these .setup files would have the same structure as the .setup files generated when clicking on Project -> New -> Other -> Oomph -> Setup Product Model (setup:Product) / Setup Project Model (setup:Project). What we get is, however, setup:ProductCatalog / setup:Installation / setup:Workspace. In other words, we don't quite get the Oomph Scopes. We only have one workspace with multiple installed plugins and multiple imported projects in it, should be a simple scenario - our expectation was that we don't need setup:Workspace or Project streams...

Can someone help, has someone done such "quick" generation of .setup models?
Re: Generate .setup from an existing project [message #1783437 is a reply to message #1783377] Tue, 13 March 2018 07:33 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 29653
Registered: July 2009
Senior Member
No, there isn't a wizard that will create complete product and project setups. Many tasks could be either part of a product setup or as part of a project setup. E.g., project setups often have p2 tasks to install tools specific to the project in addition to the base tools that are the same for all projects and hence defined in the product. There's no way to know looking at what's currently installed (which you can do with the Repository Explorer's combo which always include a choice for the installation's current profile) whether those things should be defined in the product or the project. In any case, you can very easily use the Repository Explorer to "capture" in a p2 task the requirements for what is currently installed. It's also trivial to create a Git clone task for each clone you need. And with targlets with wildcard requirements, it's very easy to import all projects in a Git clone; in fact, the project wizard will create these two things if you create a project setup in a workspace project in a Git clone. Note that most teams do not define specialized product setups; they typically just reuse one of the existing Eclipse products and define additional p2 tasks in their project setups to install additional tools in the base product.
Re: Generate .setup from an existing project [message #1783443 is a reply to message #1783437] Tue, 13 March 2018 08:57 Go to previous messageGo to next message
Wa Liu is currently offline Wa LiuFriend
Messages: 3
Registered: March 2018
Junior Member
Thanks, that helps understanding the whole concept in the beginning.

I think this will be the best approach for us too - 1. download and run the eclipse installer; 2. choose some base product, like Eclipse For Java Devs; 3. add our project.setup file in the projects page and use it. Done!

It is indeed a bit of work to declare all updates sites and p2 IUs from the old workspace that we need into the project.setup model, but after a few iterations we are ready to go on with the work ;)
Re: Generate .setup from an existing project [message #1783446 is a reply to message #1783443] Tue, 13 March 2018 09:25 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 29653
Registered: July 2009
Senior Member
Yes, it's really not so complex. Note that the use of Configurations can make all this even easier by also automating which product version to use as well as automating the selection and addition of the project stream:

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

E.g., EMF's build page is very simple steps for how anyone can reproduce EMF's development environment (in which they can reproduce the Tycho build):

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

Previous Topic:Can't install Eclipse Neon : problem with files in .p2
Next Topic:Repository Explorer
Goto Forum:
  


Current Time: Sun Nov 18 01:25:56 GMT 2018

Powered by FUDForum. Page generated in 0.02442 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top