Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Kepler Project"

m (Common Project Model)
(Reading List)
Line 19: Line 19:
 
insight into good practices for modeling a software project.
 
insight into good practices for modeling a software project.
  
* [http://maven.apache.org/ref/current/maven-model/maven.html|Apache Maven's Project Object Model (POM)]
+
* [http://maven.apache.org/ref/current/maven-model/maven.html|Apache Maven's Project Object Model (POM)] <= This is a dead link. Pete M.
 
* [[Buckminster Component Specification]]
 
* [[Buckminster Component Specification]]
 
* [http://usefulinc.com/doap Description of a Project (DOAP)] ''(See also: http://en.wikipedia.org/wiki/DOAP)''
 
* [http://usefulinc.com/doap Description of a Project (DOAP)] ''(See also: http://en.wikipedia.org/wiki/DOAP)''
 
 
  
 
=== Project Data Elements ===
 
=== Project Data Elements ===

Revision as of 20:41, 15 November 2006

The Kepler Project proposal is [here]

Meetings

11.08.2006 Conference Call

Common Project Model

What follows is meant to be the beginnings of a discussion about what sorts of data elements different tools look for in their project model. The goal here is to identify and exploit overlaps between Kepler and other Eclipse projects, in order to have a common API and set of providers to adapt external project information into the system. (By external project information I mean project data that doesn't originate within the specific Eclipse project in question, and is not therefore in a "native" format.)

If you have more information on this topic, please feel free to expand on what's already here. We're attempting to find a way to make a unified, extensible project model for general consumption...so we're going to need a lot of input.


Reading List

Below is a list of some other project models being used in the world. Though not exhaustive, these may lend some insight into good practices for modeling a software project.

Project Data Elements

Model Data Element Usage
Element Kepler Buckminster Corona Platform
Unique project ID Y ? ? ?
Project version information Y ? ? ?
Base-path of project on filesystem Y ? ? ?
Dependency metadata (project ID, version, etc.) Y ? ? ?
Configuration for project builds (indication of build tool, non-default build configuration, etc.) Y ? ? ?
Community interaction metadata (mailing list info, website URL, etc.) Y ? ? ?
Development infrastructure metadata (build server URL, etc.) Y ? ? ?

Back to the top