- 1 Kepler Proposal Documents
- 2 Meetings
- 3 Project Plan
- 4 Architecture Overview
- 5 Collaboration Model
- 6 Presentations
- 7 Upcoming Events
- 8 Bug Reports/Enhancement Requests with Requirements Info
- 9 Project-Model Reading List
Kepler Proposal Documents
The following links are to documentation on the overall architecture for the Kepler project.
What follows is 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.
I use Eclipse to develop, how does Kepler benefit me?
Think how many plugins you have to configure for each project, if you use a source control manager like SVN or CVS, if you want to use an issue tracking system, or build with external tools like Ant or Maven, and even worse if you have different configurations as the JDK version.
What can we do to alleviate this pain? By autoconfiguring several Eclipse plugins so you don't have to.
- Mylyn with the issue tracking system information
- JDT with build information like JDK version, source folders, dependencies,...
- Buckminster with dependency information
- Maven for build integration
My developers use Eclipse, why should I talk to them about Kepler?
Imagine they use a project, open source or from another department and they hit a problem. They could instantaneously know what is the mailing list for the project, or who are the developers and their contact information.
How many times did you wanted to track information about a project and ended with an Excel spreadsheet or a text document? Formalize that into a Kepler facet and you'll be able to use that information in a structured way, index it, search,... be organized
Kepler and Equinox provisioning
A Kepler model can be generated from Eclipse plugins. Equinox provisioning (p2) can also generate metadata for provisioning from Eclipse plugins.
These two examples will show how both look like:
The following are presentations that have been prepared for the Kepler project.
DevZuz presentation on proposed collaboration model - File:KeplerProposals.pdf
This will contain a list of events where Kepler project members will be talking about the project.
- Sep 25-26 Equinox Summit 2007, Ottawa, Canada. Integration with Equinox provisioning (p2)
- Oct 10-11 Eclipse Summit Europe 2007, Ludwisburg, Germany
- Nov 26-30 OSSummit, Hong Kong, China
Bug Reports/Enhancement Requests with Requirements Info
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.
- Apache Maven's Project Object Model (POM)
- Apache Maven's XML Schema. Note: Scott Lewis has created an EMF-based model from this schema.
- Installable Units Equinox p2 installable units
- Buckminster Component Specification
- Description of a Project (DOAP) (See also: http://en.wikipedia.org/wiki/DOAP)
- Gump Object Model
- Q4E Maven for Eclipse