|
|
Re: [Eclipse Installer] Select project twice (with different streams) [message #1722007 is a reply to message #1722002] |
Tue, 02 February 2016 08:50 |
Oliver Libutzki Messages: 40 Registered: September 2011 |
Member |
|
|
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 11:38 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
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
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03362 seconds