[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-core-dev] CDT ResolverModel vs ContentTypeManager
|
>
> Hi Alain,
>
> > a) The content-type mappings are global i.e. it can not be set on
> > a per project basis.
> > But so far, I've not see a real case where it is usefull.
> > Note: there is an enhancement PR for this.
>
> Will this enhancement be done in Eclipse 3.1? Will CDT drop the
> per-project file extension associations if it is not? I would not like
> to see the functionality dropped. Developers can find themselves
> working with someone else's code where "strange" file extensions are
> used, but not necessarily want these extensions to be valid in the
> projects that they create.
>
Unfortunately, there was no time frame set for this, see PR:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=85765
If this a requirement(Per-project content-type) then
we can not move to the new Content-Type framework. All we can
is provide a one way adapter i.e. ResolverModel --> Content-type
