ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

ECLIPSE IDE Tutorial - Looking at the ECLIPSE IDE Directory Structure

Updated on July 16, 2014

The Files and Sub-directories Downloaded

Technically, we should really call the process of obtaining an Eclipse IDE release as a download/comprehension process rather than an install because what the user obtains from the website, www.eclipse.org/downloads is a standard .zip file which can be decompressed by using any "vanilla" decompression utility such as WinZip.

There are a number of files and sub-directories in the zipped package and we'll step through them in the following sections.



The ECLIPSE Files for KEPLER ( Version 4.3.1)

The HTML Files

Nothing very exciting here: th epl-v10.html file is the public license and the notice.html file is the software agreement.

The Configuration File - eclipse.ini

eclipse.ini, the configuration file contains some critical information regarding the startup of ECLIPSE (.e.g. ---startup and --launcher.library lines) and some truly configurable information (e.g. the requiredJavaVersion). Below illustrated are startup failures caused by not having the -----startup jar or launcher library file available.

Configuration file error examples

The readme sub-directory

This sub-directory contains the release notes, readme,_eclipse.html, which has information about Eclipse configurations, known problems, and workarounds..

The ECLIPSE executable files

There are two files eclipse.exe and eclipsec.exe which are the ECLIPSE executables. One would generally start ECLIPSE on windows by invoking eclipse.exe. The smaller eclipsec.exe is a console version which accepts command line arguments. A simple example would be: eclipsec.exe -nosplash which initiates ECLIPSE without the fancy logo.

The Plug-Ins Folder

Just looking at the plug-ins folder can be a bit overwhelming. My installed base shows over 800+ entries, folders and jar files.

Briefly, plug-ins can be thought of as "add-on" to a base product, in this case Eclipse. The add on extends the capabilities of the product. Plug-ins extend the functionality of the product. As Eclipse was written in the JAVA programming language it followed naturally that any enhancements (plug-ins) would probably be written in JAVA as well. Most of the entries in the plug-in sub-directory are .jar (Java ARchive) files, basically compressed (.zip) files which contain sub-folders and files which make up the plug-in. A plug-in is the smallest installable and deployable software component in an ECLIPSE installation.

For the beginner, it would be overkill to dwell on other than know that a plug-in may used when you use a feature which triggers the plug-in code. Plug-ins provide additional capabilities and customization to the ECLIPSE product.


The p2 folder

The p2 folder is associated with a subproject within the ECLIPSE development effort. The p2 effort can best be described as a " provisioning platform", that is an enabling platform, for OSGi (Open Service Gateway Initiative), a set of standards for component implementation, documentation, and deployment. The emphasis of p2 in the context of ECLIPSE in part was better installation and software updating from a user perspective. For an ECLIPSE user it is most evident how software updates are handled.

The dropin folder

The drop-in folder is identical to the plug-in folder in terms of functionality.. A drop-in like a plug-in is an extension to the ECLIPSE product. Developers use the drop-in folder for extension to ECLIPSE which are being tested for example. In simple terms, a drop-in has less formal support, such a supported site for its inclusion in the product.

The feature folder

A feature in ECLIPSE can be thought of as a logically connected set of plug-ins which have no external dependencies. For example, mylyn, the ECLIPSE task management subsystem, is implemented by a set of features: task features, team related features and notifications.

The artifacts.xml file


The Eclipse 'p2' install system uses this file as repository of installable artifacts. The file is sometimes compressed in to an jar file, artifacts.jar.

The .eclipseproduct file

A file which contains the product name, id, and version.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)