Jump to: navigation, search

Difference between revisions of "Kepler Project"

m (Common Project Model)
(Common Project Model)
Line 12: Line 12:
 
'''Reading List:'''
 
'''Reading List:'''
  
* [[http://maven.apache.org/ref/current/maven-model/maven.html|Maven Project Object Model (POM)]]
+
* [http://maven.apache.org/ref/current/maven-model/maven.html|Apache Maven's Project Object Model (POM)]
* Buckminster CSPEC
+
* [[Buckminster Component Specification]]
* DOAP
+
* [http://usefulinc.com/doap|Description of a Project (DOAP)] ''(See also: [Wikipedia entry|http://en.wikipedia.org/wiki/DOAP])''
  
 
{| border="1" cellpadding="5" cellspacing="0"
 
{| border="1" cellpadding="5" cellspacing="0"

Revision as of 11:33, 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.)

Reading List:

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 ? ? ?