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 17: Line 17:
  
 
==Deliverables==
 
==Deliverables==
*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.
  
 
==Terminology==
 
==Terminology==

Revision as of 12:23, 27 May 2007

This project aims to design an Eclipse plugin that allows the binaries required by other Eclipse plugins to be automatically located.

Project Lead:

  • Ogechi Nnadi (IRC: onnadi3)

Mentors:

This is one of the selected projects for Google's Summer of Code program in 2007. The original application can be found here.


About

Meeting Time

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

Deliverables

  • 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.

Terminology

Use cases

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

Architecture

Back to the top