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 (Deliverables)
Line 20: Line 20:
  
 
*1 June 2007 Create a compilable plug-in in the cvs repository  that takes a collection of possible URIs and returns any JDKs found in those locations.
 
*1 June 2007 Create a compilable plug-in in the cvs repository  that takes a collection of possible URIs and returns any JDKs found in those locations.
 +
 +
==Requirements==
 +
===Must===
 +
===Should===
 +
===Nice to Have===
  
 
==Applications / Services that should be detected==
 
==Applications / Services that should be detected==

Revision as of 10:31, 9 June 2007

About

This project aims to design an Eclipse plugin that allows the binaries required by other Eclipse plugins to be automatically located. The source code shall be released under the Eclipse Public License. This is one of the selected projects for the 2007 Google Summer of Code. The original application can be found here.

Project Lead:

Mentors:

Meeting Time

We meet on Saturdays at 9:30am EDT/7:00pm IST in the #eclipse-soc channel on irc.freenode.net.

Here are our meeting logs.

Deliverables

Our code is currently hosted in the eclipse-incub project at SourceForge, under the module name, service-discovery.

  • 6 June 2007 Implement a simple fs finder connected to org.eclipse.discovery via an OSGi service, and an exemplary consumer that uses this finder to discover JDKs.
  • 1 June 2007 Create a compilable plug-in in the cvs repository that takes a collection of possible URIs and returns any JDKs found in those locations.

Requirements

Must

Should

Nice to Have

Applications / Services that should be detected

  • JDK/JRE, GCC, Python, Perl, etc.
    • Blobs of documentation (javadoc, PoD, Doxygen), preferably linked to the resources they document
  • Apache Http server, Apache Tomcat, Jetty
  • bzip2,gzip,rar,arj,... (for deployment and browsing into archives)
    • An EFS provider that allows browsing into such archives like folders might be a nice side project
  • Cygwin (including auto-detect of cygwin mount points and path translation)
    • An EFS provider that shows the cygwin local filesystem might be a nice side project

Back to the top