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 "An auto-configuration plugin for Eclipse"

m
(Use cases)
Line 18: Line 18:
  
 
==Use cases==
 
==Use cases==
 +
===Applications / Services that should be detected===
 +
*JDK/JRE, GCC, Python, Perl, etc.
 +
*Apache Http server, Apache Tomcat, Jetty
  
 
==Architecture==
 
==Architecture==

Revision as of 13:06, 21 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. The original application can be found Google Summer of Code 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 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

Applications / Services that should be detected

  • JDK/JRE, GCC, Python, Perl, etc.
  • Apache Http server, Apache Tomcat, Jetty

Architecture

Back to the top