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

["Andrey Loskutov" <loskutov@xxxxxx>]

I fully agree with Tom.

In one of the my answers I've already suggested to think about something like boolean IResource::isNested() API.

 

Regarding isHidden() question: NO.

As javadoc on setHidden() says: Hidden resources are invisible to most clients.

 

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 

 

Gesendet: Mittwoch, 22. Januar 2020 um 09:52 Uhr
Von: "Tom Schindl" <tom.schindl@xxxxxxxxxxxxxxx>
An: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Betreff: Re: [platform-dev] Marking nested projects as derived, what are the risks?

Hi,

 

I think the only correct solution is to enhance the core API and then adjust all components. Is it a lot of work? yes! But I think it is the only viable long term solution.

 

Tom
 

Von meinem iPhone gesendet

 

Am 22.01.2020 um 09:34 schrieb Mickael Istria <mistria@xxxxxxxxxx>:
 



Hi all,

 

So I'm making progress in my thoughts around those issues.

What about hidden resources? To rephrase "Marking folders for nested projects as hidden, what are the risks?"

 

I'm not really sure of what hidden implies under the hood, but the documentation seems pretty flexible in usage. Maybe it's just the exact match for nested projects? m2e has is available as "Experimental", and Till found a few (fixable) issues in https://bugs.eclipse.org/bugs/show_bug.cgi?id=500624#c14 . Before investing more in trying to fix some of those issues, I'd like some other opinions on whether it seems like a good track to follow.

 

Thanks in advance