| [Eclipse Installer] Select project twice (with different streams) [message #1721999] |
Tue, 02 February 2016 03:09  |
Eclipse User |
|
|
|
Hi,
currently it's not possible to select a project twice with different streams.
You have to install one stream first and then you can add another stream of the same project in your previously installed Eclipse application.
Is this just a "missing feature" in the Eclipse Installer?
Kind regards
Oliver
|
|
|
|
| Re: [Eclipse Installer] Select project twice (with different streams) [message #1722007 is a reply to message #1722002] |
Tue, 02 February 2016 03:50  |
| Eclipse User |
|
|
|
Ed Merks wrote on Tue, 02 February 2016 03:26Oliver,
No, it just doesn't match the intent of streams. They're generally
expected to correspond to streams/branches in a version control system,
and of course from that point of view, you can only check out one
stream/branch at a time.
Hi Ed,
I do not agree as it's very common to develop different branches of a project in the same Eclipse installation. The m2e tooling (and Oomph's Maven Import task) provides possibilities to derive the project names by using a template like [artifactId]-${scope.project.stream.label}.
So, imho, it's quite common to use the same installation for different branches of the same project.
If you think about Plugin-development with a target platform your statement is correct, but not generally.
Kind regards
Oliver
|
|
|
| Re: [Eclipse Installer] Select project twice (with different streams) [message #1722033 is a reply to message #1722007] |
Tue, 02 February 2016 06:38 |
| Eclipse User |
|
|
|
Oliver,
Comments below.
On 02.02.2016 09:50, Oliver Libutzki wrote:
> Ed Merks wrote on Tue, 02 February 2016 03:26
>> Oliver,
>>
>> No, it just doesn't match the intent of streams. They're generally
>> expected to correspond to streams/branches in a version control
>> system, and of course from that point of view, you can only check out
>> one stream/branch at a time.
>
> Hi Ed,
>
> I do not agree as it's very common to develop different branches of a
> project in the same Eclipse installation. The m2e tooling (and Oomph's
> Maven Import task) provides possibilities to derive the project names
> by using a template like [artifactId]-${scope.project.stream.label}.
I'm very doubtful. I'm not sure how the PDE can cope with two different
projects that have the same bundle ID. How can dependencies be resolved
if there is more than one bundle with a given ID. So I get the sense
that this is a manufactured scenario, not a real one. Certainly a
single clone can only have one checkout, at least right now, and I can't
imagine how PDE can cope with multiple versions of the same bundle at
the same time in the workspace.
>
> So, imho, it's quite common to use the same installation for different
> branches of the same project.
All in the same workspace and at the same time? I don't get it at all.
It makes no sense to me.
>
> If you think about Plugin-development with a target platform your
> statement is correct, but not generally.
Yes, that's mostly what I think about. And even without that, it seems
to me you'd need multiple clones to have different branches active at
the same time. It all seems not common at all.
>
> Kind regards
> Oliver
|
|
|
|
|
| Re: [Eclipse Installer] Select project twice (with different streams) [message #1722657 is a reply to message #1722052] |
Mon, 08 February 2016 01:46 |
| Eclipse User |
|
|
|
Ed Merks wrote on Tue, 02 February 2016 08:52
Are we taking projects now or streams still? If streams then, yes, I
have a big problem entertaining the associated complexity of allowing
users to choose several streams from the same project simultaneously.
It doesn't generally make any sense, and it would require a great deal
of redesign work...
Hi Ed,
thanks for your answer. I will recommend to use one installation per branch.
|
|
|
Powered by
FUDForum. Page generated in 0.03972 seconds
Home