[platform-dev] Marking nested projects as derived, what are the risks?

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi all,

In m2e, BuildShip or even for the Open Resources and other views, one issue appears often: duplication of resources in visible area, confusing users.

The m2e issue about it is https://bugs.eclipse.org/bugs/show_bug.cgi?id=500624 .

Eclipse Platform has the idea of "derived" resources which are well integrated in several views/dialogs so they can be hidden. So I'm curious about what would be the impact of marking nested projects as derived? Let's say I have A and A/B imported as projects in workspace, what bad things could happen if the B folder inside A is marked as derived when A/B is here?

Is the derived flag affecting some core stuff or only UI?

Would it be do-able to have a property to control whether to automatically mark such folders as derived when they're nested project, and let users manage it or is it too much risk...?

Thanks in advance for your insights.

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers