Skip to main content
Jump to: navigation, search

Difference between revisions of "An auto-configuration plugin for Eclipse"

(New page: ==About== Many Eclipse plugins require the user to specify the location of certain programs or services running locally in order for them to work. Having humans do this is unnecessary sinc...)
 
Line 1: Line 1:
 +
Project Lead:
 +
Ogechi Nnadi (IRC: onnadi3)
 +
 +
Mentors:
 +
Remy Chi Jian Suen (IRC: rcjsuen),
 +
Markus Alexander Kuppe (IRC: lemmy)
 +
Blog: [http://www.lemmster.de/blog/?feed=rss2&cat=9 http://www.lemmster.de]
 +
 +
This project is part of the [[Google Summer of Code 2007]]
 +
 +
 
==About==
 
==About==
 
Many Eclipse plugins require the user to specify the location of certain programs or services running locally in order for them to work. Having humans do this is unnecessary since services are commonly installed in only a few fixed locations. Thus I propose writing an Eclipse plugin that uses a number of heuristics to locate local services that other Eclipse plugins need. I also propose including a number of utilities that enable developers to easily write, extend, and distribute these service 'scanners.'
 
Many Eclipse plugins require the user to specify the location of certain programs or services running locally in order for them to work. Having humans do this is unnecessary since services are commonly installed in only a few fixed locations. Thus I propose writing an Eclipse plugin that uses a number of heuristics to locate local services that other Eclipse plugins need. I also propose including a number of utilities that enable developers to easily write, extend, and distribute these service 'scanners.'
 +
 +
==Deliverables==
  
 
==Terminology==
 
==Terminology==

Revision as of 11:24, 20 April 2007

Project Lead: Ogechi Nnadi (IRC: onnadi3)

Mentors: Remy Chi Jian Suen (IRC: rcjsuen), Markus Alexander Kuppe (IRC: lemmy) Blog: http://www.lemmster.de

This project is part of the Google Summer of Code 2007


About

Many Eclipse plugins require the user to specify the location of certain programs or services running locally in order for them to work. Having humans do this is unnecessary since services are commonly installed in only a few fixed locations. Thus I propose writing an Eclipse plugin that uses a number of heuristics to locate local services that other Eclipse plugins need. I also propose including a number of utilities that enable developers to easily write, extend, and distribute these service 'scanners.'

Deliverables

Terminology

Use cases

Architecture

Back to the top