Re: [platform-dev] Marking nested projects as derived, what are the risk

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

That's a very limited
experiment.

What happens if
I delete all derived resources?

Dani



From:
       Mickael
Istria <mistria@xxxxxxxxxx>
To:
       "Eclipse
platform general developers list." <platform-dev@xxxxxxxxxxx>
Date:
       21.01.2020
11:47
Subject:
       [EXTERNAL]
Re: [platform-dev] Marking nested projects as derived,      
 what are the risks?
Sent
by:        platform-dev-bounces@xxxxxxxxxxx

---

On Tue, Jan 21, 2020 at 11:34 AM Daniel
Megert <daniel_megert@xxxxxxxxxx>
wrote:
The Javadoc says
it all.

My experiment shows the Javadoc isn't
really accurate in practice with EGit.
Also, with the proposal:
* "Derived resources are not original
data, and can be recreated from other resources." is true as the duplicate
in nested project can be perceived as the original data
* "a team provider should assume
that the resource is not under version and configuration management by
default. That is, the resource should only be stored in a team repository
if the user explicitly indicates that this resource is worth saving."
it's the case if user explicitly says the resource is worth saving in the
parent project (moreover, EGit ignores that apparently as it prefers the
.gitignore)

I do not fully see the Javadoc as being
against that change, and my experiment seems to confirm that the proposal
of marking nested project folders as derived seems to fit int the main
invariants enforced by the javadoc._______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev