Hi Mickael Indeed and all those diverse actions
can be orchestrated by the XXXNature.configure() which currently has to
be 100% cloned; an AbstractProjectNatue could offer standard functionality.
If XXXNature.configure() neglects to invoke project.setDescription(), no
XXX nature would actually be added leaving XXXNature.configure() as a transient
tool for some irregular form of configuration. Regards
Ed Willink

On 10/01/2018 09:36, Mickael Istria wrote:

On Wed, Jan 10, 2018 at 10:29 AM, Ed
Willink <ed@xxxxxxxxxxxxx>
wrote:Suggest that an optional "extensions"
element for an "org.eclipse.core.resources.natures" extension
point could identify the file extensions to which an auto-add-nature could
apply.

I think natures are too restraining here.
While it's used in most cases, there are other ways an editor can configure
a projet or its own enablement (preferences, project settings, a builder,
starting a Run configuration, show a wizard...). I believe the diversity
of possible actions makes it almost impossible to find a generic solution
to this problem that can cover all legacy and future stories.-- Mickael IstriaEclipse
IDE developer, at Red
Hat Developers communityElected Committer Representative at the
Eclipse
Foundation board of directors