> I imagine It's the 90% of use-cases experiment. Here I completely disagree. You have no clue what people do with derived resources.
As per the Javadoc a builder or something else must be capable to bring back the deleted stuff. If there are already issues with nested projects then this is a different case and not reason/excuse to use the derived state. Dani From: Mickael Istria <[email protected]> To: "Eclipse platform general developers list." <[email protected]> Date: 21.01.2020 12:11 Subject: [EXTERNAL] Re: [platform-dev] Marking nested projects as derived, what are the risks? Sent by: [email protected] On Tue, Jan 21, 2020 at 12:03 PM Daniel Megert <[email protected]> wrote: That's a very limited experiment. I imagine It's the 90% of use-cases experiment. What happens if I delete all derived resources? Removing resources is already a tricky case in current state with duplication (duplicated resources are still listed although their backend filesystem doesn't exist any more, resulting in erased editor content or editor suddenly marked as dirty and not able to save properly...). I don't get how deleting a derived resource would be any different. Which area do you specifically have in mind that could become more faulty? _______________________________________________ platform-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________ platform-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
