| How to model update site <-> Eclipse version dependency [message #1405480] |
Thu, 07 August 2014 08:53  |
Eclipse User |
|
|
|
Hi,
the Oomph installer works in two steps: First, you select a product, then you select one or more projects.
As one of my projects requires Subversive to be installed, this two-step approach causes trouble for me: I want to install the SVNKit connector but there exist different update sites to use for Luna and Kepler, respectively. In other words, during step two I need to know which Eclipse version (Luna or Kepler) was picked during step one.
Is there any way to model this with Oomph other than having labels like "My Project (for Eclipse Luna)" and "My Project (for Eclipse Kepler)" and let the user pick the right one?
|
|
|
| Re: How to model update site <-> Eclipse version dependency [message #1405538 is a reply to message #1405480] |
Thu, 07 August 2014 11:14  |
| Eclipse User |
|
|
|
Andreas,
Comments below.
On 07/08/2014 2:53 PM, Andreas Sewe wrote:
> Hi,
>
> the Oomph installer works in two steps: First, you select a product,
> then you select one or more projects.
>
> As one of my projects requires Subversive to be installed, this
> two-step approach causes trouble for me: I want to install the SVNKit
> connector but there exist different update sites to use for Luna and
> Kepler, respectively. In other words, during step two I need to know
> which Eclipse version (Luna or Kepler) was picked during step one.
Can't you include both update sites? The installer will generally try
to find a solution that meets all the requirements.
>
> Is there any way to model this with Oomph other than having labels
> like "My Project (for Eclipse Luna)" and "My Project (for Eclipse
> Kepler)" and let the user pick the right one?
Try including both update sites; presumably the connector plugins have
restrictions on where they allow themselves to be installed so the
appropriate version will be picked automagically...
|
|
|
Powered by
FUDForum. Page generated in 0.05947 seconds
Home