LOCKER: eclipse-sdk_v4.8m4 FILE: /mit/eclipse-sdk_v4.8m4/README.athena CONTENTS: Eclipse 4.8m4 version locker DESCRIPTION: Eclipse is a kind of universal tool platform - an open, extensible IDE. It's major use is a Java IDE- it uses Java in the "current" Java locker for this purpose. HOW TO RUN: COMMAND: add eclipse-sdk; eclipse [-ver 4.8m4] FROM DASH: no INTERFACES: GUI VERSIONS: For Linux 64: Eclipse version 4.8M4 DEPENDENCIES: uses Java in the "current" Java locker DATAFILES: Platform-independent, but configuration files may be platform- and version-dependent LICENSE SERVER: no ------------------------------------------------------------------------- SUPPORT ISSUES -- I/S SUPPORT: CONSULTING: none TRAINING: internal tutorial, examples DOCUMENTATION: online documentation accessible from within the GUI OTHER SUPPORT: CONSULTING: (none) TRAINING: (none) DOCUMENTATION: http://www.eclipse.org/documentation WEB PAGE: http://www.eclipse.org BUG REPORTS: Use sendbug ------------------------------------------------------------------------- LEGAL ISSUES -- STATUS: under Eclipse Public License SITES: any RIGHTS: you are granted a worldwide, royalty-free license to use, copy and distribute this application and derivative works of it, in source code or object code form. RESTRICTIONS: if you distribute or contribute to this application certain requirements apply- please see complete license for details (https://www.eclipse.org/legal/epl-v10.html) DOCUMENTATION: documentation may be used and distributed in the same way as the software. NOTE: the above applies to Eclipse proper; plugins can have individual licenses, some of them more restrictive. ------------------------------------------------------------------------- ABOUT THIS LOCKER -- MAINTAINER(S): swmaint (group), alexp DIRECTORY STRUCTURE: arch - arch hierarchy distrib/amd64_ubuntu1404/eclipse - Linux 64 top level /configuration - configuration files /dropins - currently empty eclipse - main binary /features - component descriptions /p2 - p2 files /plugins - components (in Java) /readme - release notes MODIFY HISTORY: 1/8/18 - Alex Prengel Created this README.athena, initial locker setup MISCELLANEOUS: Features installed is the 4.8m4 Linux 64 GTK SDK, as well as: CDT (C/C++ projects) 9.4.0 GEF 5.0.2 Pydev 6.2.0 Subclipse 4.2.3 All files except for the main eclipse binary should be platform-independent. Metadata files stored in the workspace/.metadata directory are platform- and version-dependent. To accomodate this, the configuration has been set up for a common workspace directory using AFS @sys links to distinguish platform versions when the workspace is in AFS, but not otherwise. A default choice of $HOME/workspace will be proposed when you run, but you can override this by picking a different directory. ****************************************************************************** IMPORTANT: Due to the way we have set this up for our environment, users should not select File -> Switch Workspace, if switching to a workspace in AFS that has not been used before, but rather should restart Eclipse and select that workspace at the prompt requesting a workspace choice before Eclipse starts. If you don't do this your metadata files in your workspace may get corrupted. ****************************************************************************** Eclipse will store various settings in a directory .eclipse in your home directory. We have also used AFS @sys links to distinguish this by Eclipse version and platform, when your home directory is in AFS. It also stores settings in "dot" directories in your workspace directory. Due to complications in switching platform configurations, it is advisable to keep your project work on a single platform (Linux 32 or 64) for the duration of a given project, if you can. The actual data files in your workspace directories should be platform-independent. ****************************************************************************** INSTALLING ADDITIONAL PLUGINS: It's not practical for us to install every possible plugin globally- there are hundreds of them. users can install them individually, to locations where they have write permission, as follows: If an update site exists, you must obtain the URL (an update site often has a file site.xml, and directories "features" and "plugins" at the top level). Run "Install New Software", enter a name and URL in the "Add Repository" dialog, pick the features you want installed from the list that appears below and click "Install", accept license terms if you agree with them, and let it install. If no update site exists, you must manually download an archive containing the plugin, usually in zip format; you need to unpack this into a local "plugins" directory, taking care that the directory structure in the zip file matches that in your "plugins" directory (often the zip file will have "plugins" as subdirectory immediately below the top level). In either case, you may need to set a number of preferences manually to fully install the plugin- the authors of the plugin need to tell you exactly what to do. You can check if Eclipse recognizes the plugin by running "Help" -> "About Eclipse SDK" -> "Installation Details"; you should see it in the plugin list. Unfortunately configuring plugins is tricky- you might see it there but still not be able to run it from within the main GUI.