| Setup centralized setup environment [message #1701584] |
Tue, 14 July 2015 09:40  |
 Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Hello there,
my company wants to give Eclipse Oomph a try. Basically, we want to have a central setup environment for all our developers to make future project setups easier and faster.
So, I already testet the setups itself locally and everything works fine.
Now, we want to get those things into our network. Unfortunately, I am not able to understand the documentation, I really hope for an improvement and step by step explanation on how to do it. (Maybe I provide it myself, once I understood the process =) )
Here is what I understood so far:
When we start the Oomph installer, we have to choose a product. In the standard version I have a list of products from eclipse.org. As far as I understood this is more or less a basic template for the eclipse client.
Now, we want to have an own list of products for our company to provide our developers with Eclipse versions.
After that is chosen, we can select the project setups. In the standard we have have a list from eclipse.org. I already used it to drag&drop my setup manually into the <User> section and install it. Here, we want a predefined list in the installer from which the developer can choose the installation.
Now my questions:
- how can I setup a list of products for our company?
I assume you have to define a catalogue or an index which is basically an xml file which is located somewhere in the network (file-share?) and we have to tell our installer via config files where to find it.
- how can I setup a list of project setups for our company?
Basically the same question, I assume I have to define some kind of catalogue or something which is located in the network and tell the installer where to find it.
Could you please provide some information on what to do? Also, what exactly is the bundle pool in this context? Does it provide the catalogues or something?
I would really appreciate some help here.
Thanks in advance.
|
|
|
| Re: Setup centralized setup environment [message #1701625 is a reply to message #1701584] |
Tue, 14 July 2015 13:51  |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Comments below.
On 14/07/2015 3:06 PM, Matthias Nicklisch wrote:
> Hello there,
>
> my company wants to give Eclipse Oomph a try. Basically, we want to
> have a central setup environment for all our developers to make future
> project setups easier and faster.
>
> So, I already testet the setups itself locally and everything works fine.
>
> Now, we want to get those things into our network. Unfortunately, I am
> not able to understand the documentation, I really hope for an
> improvement and step by step explanation on how to do it. (Maybe I
> provide it myself, once I understood the process =) )
:-P
> Here is what I understood so far:
>
> When we start the Oomph installer, we have to choose a product. In the
> standard version I have a list of products from eclipse.org. As far as
> I understood this is more or less a basic template for the eclipse
> client.
> Now, we want to have an own list of products for our company to
> provide our developers with Eclipse versions. After that is chosen,
> we can select the project setups. In the standard we have have a list
> from eclipse.org. I already used it to drag&drop my setup manually
> into the <User> section and install it. Here, we want a predefined
> list in the installer from which the developer can choose the
> installation.
>
> Now my questions:
>
> - how can I setup a list of products for our company?
Any -D option that starts with oomph.redirection. will be treated as a
redirection. For example, in our launch configuration for debugging the
installer we have
-Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->${file_uri:${resource_loc:/setups}}/
This uses EMF's URIMap, so the fact they end with "/" makes them a
folder redirection. You could redirect just the
org.eclipse.oomph.setup.internal.core.SetupContext.INDEX_SETUP_LOCATION_URI
to your own web location.
> I assume you have to define a catalogue or an index which is
> basically an xml file which is located somewhere in the network
> (file-share?) and we have to tell our installer via config files where
> to find it.
Yes, likely via a -D (or config.ini property) as explained above to
redirect the entire index.
> - how can I setup a list of project setups for our company?
The index has lists of product catalogs and lists of project catalogs.
If you redirect the index, you can control everything else that's available.
> Basically the same question, I assume I have to define some kind of
> catalogue or something which is located in the network and tell the
> installer where to find it.
If it finds the index, it will follow all your links from there.
>
> Could you please provide some information on what to do? Also, what
> exactly is the bundle pool in this context?
The bundle pool is an orthogonal concept. It's supported directly by p2
and explained by their documentation:
https://wiki.eclipse.org/Equinox/p2/Getting_Started
> Does it provide the catalogues or something?
No, it's just a p2 management technology to share files across multiple
installations (and to avoid downloading them multiple times).
>
> I would really appreciate some help here.
>
> Thanks in advance.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.02855 seconds
] 
Search
Help
Register
Login
Home
