Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Faceted Project Framework » Why hasn't it been pushed down into Platform before?
Why hasn't it been pushed down into Platform before? [message #2390] Tue, 28 October 2008 13:44 Go to next message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 983
Registered: July 2009
Senior Member
Have there been any previous attempts to push Faceted Project Framework
down into the Platform before? Have any of the discussions / arguments
around that been recorded for interested readers?

On another note, reading the article on
http://www.eclipse.org/articles/Article-BuildingProjectFacet s/tutorial.html
I notice that some of the extension point functionality (e.g.
Expressions) might now be take over by existing core functionality (e.g.
core expressions).

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 Member
http://www.eclipse.org/dsdp/tm
Re: Why hasn't it been pushed down into Platform before? [message #2420 is a reply to message #2390] Tue, 28 October 2008 13:53 Go to previous message
Konstantin Komissarchik is currently offline Konstantin Komissarchik
Messages: 940
Registered: July 2009
Senior Member
> Have there been any previous attempts to push Faceted Project Framework
> down into the Platform before? Have any of the discussions / arguments
> around that been recorded for interested readers?

Yeah. That has been tried before. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160245 for the discussion.

> On another note, reading the article on
> http://www.eclipse.org/articles/Article-BuildingProjectFacet s/tutorial.html
> I notice that some of the extension point functionality (e.g.
> Expressions) might now be take over by existing core functionality (e.g.
> core expressions).

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.
Re: Why hasn't it been pushed down into Platform before? [message #571549 is a reply to message #2390] Tue, 28 October 2008 13:53 Go to previous message
Konstantin Komissarchik is currently offline Konstantin Komissarchik
Messages: 940
Registered: July 2009
Senior Member
> Have there been any previous attempts to push Faceted Project Framework
> down into the Platform before? Have any of the discussions / arguments
> around that been recorded for interested readers?

Yeah. That has been tried before. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160245 for the discussion.

> On another note, reading the article on
> http://www.eclipse.org/articles/Article-BuildingProjectFacet s/tutorial.html
> I notice that some of the extension point functionality (e.g.
> Expressions) might now be take over by existing core functionality (e.g.
> core expressions).

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.
Previous Topic:Why hasn't it been pushed down into Platform before?
Next Topic:Welcome to eclipse.fproj
Goto Forum:
  


Current Time: Fri Aug 29 18:33:25 EDT 2014

Powered by FUDForum. Page generated in 0.01602 seconds