Jump to: navigation, search

Difference between revisions of "Kepler Project"

m (Project-Model Reading List)
Line 23: Line 23:
  
 
* [http://maven.apache.org/ref/current/maven-model/ Apache Maven's Project Object Model (POM)]   
 
* [http://maven.apache.org/ref/current/maven-model/ Apache Maven's Project Object Model (POM)]   
* [http://maven.apache.org/maven-v4_0_0.xsd Apache Maven's XML Schema].  '''Note''':  Scott Lewis has created an EMF-based model from this schema.
+
** [http://maven.apache.org/maven-v4_0_0.xsd Apache Maven's XML Schema].  '''Note''':  Scott Lewis has created an EMF-based model from this schema.
 
* [[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)''
 
* [http://gump.apache.org/metadata/index.html Gump Object Model]
 
* [http://gump.apache.org/metadata/index.html Gump Object Model]

Revision as of 11:49, 30 November 2006

Kepler Proposal Documents

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.


Project-Model 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.