Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [technology-pmc] Project Proposal: Faceted Project Framework
If possible, I would like to include support for automation of faces management by third parties as part of the scope.

In other words, currently Eclipse IAM (and, as far as I can tell, m2e) use the faceted project framework to configure an eclipse project from external metadata (maven's pom.xml). I think that this use case should be explicitly included in the proposal (currently this is possible, but could be easier).


El 15/10/2008, a las 18:45, Konstantin Komissarchik escribió:

Good point. Attached is a revised copy that hopefully addresses this and other comments.

 

1. Better scope section.

2. Turned the old scope section into the “Initial Components” section.

3. Added some statements about possible relationship to E4.

4. Added some clarifying statements regarding relationship to Project Natures from the Platform.

5. Clarified the relationship with WTP. In particular, made it clear that no immediate change at WTP will take place as the result of this project’s creation and that adoption of this project by WTP carries with it requirements specified by WTP (as in providing a robust backwards compatibility layer).

6. Added Eclipse IAM project as an interested party.

 

Let me know if anyone has further comments before this is sent to EMO.

 

<image001.gif>
Konstantin Komissarchik | Consulting Member of Technical Staff
Phone: +1 425 201 1795 | Mobile: +1 206 898 0611
Oracle Eclipse Tooling
411 108th Ave NE, Suite 2100 | Bellevue, WA 98004

 

From: Bjorn Freeman-Benson [mailto:bjorn.freeman-benson@xxxxxxxxxxx]
Sent: Wednesday, October 15, 2008 8:28 AM
To: konstantin.komissarchik@xxxxxxxxxx; Technology PMC
Subject: Re: [technology-pmc] Project Proposal: Faceted Project Framework

 

Konstantin,
The "scope" section of the project proposal is the most important section (yes, I know, that's not obvious and it sure would be helpful to have your handy "propose a project" form to make that clear), and the scope section needs to describe the encompassing scope of the project and not a plan. The scope defines the space the project will work in - the whole space, not just today's space. Thus the scope section should not include any time-based words such as "at least" and "future".

Additionally, the scope section of this proposal needs to be fleshed out a little to explain the project to Eclipse community members who are not code insiders. In fact, the purpose the project proposal is to announce the new project to the larger Eclipse community and that community includes people in other projects who are not directly familiar with this code and it includes the marketing and business people at our various member companies - people who have no experience at all with the code. The scope section needs to be readable by all those people.

- Bjorn

Konstantin Komissarchik wrote:

Scope

The project would be composed of at least two components:

  1. Core Framework
    1. API for building facets and manipulating faceted projects.
    2. UI for manipulate faceted projects. Includes a project properties page for adding and removing facets and a base wizard implementation for creating new faceted projects.
    3. Documentation for writing facets.
  2. JDT Enablement
    1. Java facet that's built around JDT's Java Project Nature.
    2. Modeling of runtimes that are JVM-based.
    3. Tools for making it easier to build facets for Java-based technologies. Includes tools for helping facets manage libraries.
  3. Other Enablement (future)
    1. Integration with other Eclipse Projects. This is an area for possible future work.

 

--
[end of message]

<image001.gif><fproj.html>
_______________________________________________
technology-pmc mailing list

Back to the top