Why hasn't it been pushed down into Platform before?https://www.eclipse.org/forums/index.php/mv/msg/912/2390/#msg_2390
down into the Platform before? Have any of the discussions / arguments
around that been recorded for interested readers?

Are there any plans for refactoring in order to better align with the
Platform? Are there any plans for changing the namespace of the
extension points (from *.wst.* into some thing different)?

Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Memberhttp://www.eclipse.org/dsdp/tm]]>Martin Oberhuber2008-10-28T17:44:03-00:00Re: Why hasn't it been pushed down into Platform before?https://www.eclipse.org/forums/index.php/mv/msg/912/2420/#msg_2420
> down into the Platform before? Have any of the discussions / arguments
> around that been recorded for interested readers?

Which part of the API are you referring to? The core expressions framework
is used in various places of the API today. The framework contributes
various property testers.

> Are there any plans for refactoring in order to better align with the
> Platform?

While there are no specific plans regarding this today, it's always an
option if specific issues are raised.

> Are there any plans for changing the namespace of the extension points
> (from *.wst.* into some thing different)?

Definitely. In fact the *.wst.* namespace that's in use today is reserved
for backwards compatibility with the API as it exists in WTP. My current
thinking is that the new framework will live in org.eclipse.fproj
namespace, but haven't checked with EMO yet.]]>Konstantin Komissarchik2008-10-28T17:53:36-00:00Re: Why hasn't it been pushed down into Platform before?https://www.eclipse.org/forums/index.php/mv/msg/912/571549/#msg_571549
> down into the Platform before? Have any of the discussions / arguments
> around that been recorded for interested readers?

Which part of the API are you referring to? The core expressions framework
is used in various places of the API today. The framework contributes
various property testers.

> Are there any plans for refactoring in order to better align with the
> Platform?

While there are no specific plans regarding this today, it's always an
option if specific issues are raised.

> Are there any plans for changing the namespace of the extension points
> (from *.wst.* into some thing different)?

Definitely. In fact the *.wst.* namespace that's in use today is reserved
for backwards compatibility with the API as it exists in WTP. My current
thinking is that the new framework will live in org.eclipse.fproj
namespace, but haven't checked with EMO yet.]]>Konstantin Komissarchik2008-10-28T17:53:36-00:00