Eclipse Standard Installation
From Blue-IT.org Wiki
Important Links
Plugins
API
Eclipse 3.4 Ganymed
--Apos 21:11, 3 July 2008 (CEST)
Concerning installation issues nothing changed dramatically. See above.
SWT / JFace
Project setup
Using SWT/JFace for a project needs adding the following to the build path of the project.
Under Project -> Properties -> Java Build Path -> Libraries add the following variables (by extending the ECLIPSE_HOME variable)
- org.eclipse.core.commands
- org.eclipse.core.runtime
- org.eclipse.equinox.common
- org.eclipse.jface
- org.eclipse.osgi
- org.eclipse.swt
- org.eclipse.swt.your_architecture (e.g. gtk.linux...)
If you are using other
View javadoc of source code
- Postet this solutin in eclipseplugincentral.com forum
It seams not to be enough to add the sources to the java build path (project->properties). For me (and I am under linux) I have to:
- Focus the considered classname with the cursor
- Press F3
-> The Class file editor opens
- Read the "Source not found ..." message
- Press the "Attach source..." button
-> The dialog for source attachment configurarion opens
- Press "Variable" button and add "ECLIPSE_HOME" from the next dialog. Close this with OK.
- Back to the previous source attachment configuration dialog, press "Extension ..."
- Locate your source file with e.g. "*swt*source*" in the search field an apply.
JDocEditor
An Eclipse plugin that contributes a WYSIWYG JavaDoc editor to the JDT platform.
A nearly complete rewrite, now using pure SWT controls to achieve faster start-up, more efficient run-time operation, and lower operating resource requirements.
The key change is complete replacement of the SWT_AWT bridge and Swing HtmlEditorKit controls with a StyledText-based HTML WYSIWYG editor control, with supporting CSS query and spelling correction engines.
Other architectural changes include relaxing reliance on the Content Outline View and removes direct reliance on Eclipse internal packages. JDocEditor now properly recognizes navigation events from the current active JDT editor as well as the Outline, and the Outline is not required to be open to use JDocEditor. This version should be fully compatibile with JDT-based Eclipse derivatives, such as WebSphere.**
(**Description taken from homepage)
Jautodoc
JAutodoc is an Eclipse Plugin for automatic adding Javadoc and file headers to your source code. It optionally generates initial comments from element name. Starting with Release 1.3 of JAutodoc it is possible to define Velocity templates for Javadoc and file headers.**
(**Description taken from homepage)
Doclipse
Doclipse is an Eclipse plug-in to help you write Java source files with Javadoc tags, either for documentation purposes or to be processed by a tool such as EJBGen or XDoclet. New tags can be added to the plug-in by writing XML files defining the new tags and their attributes.**
(**Description taken from homepage)
Eclipse 3.3 Europa
A lot changed in version 3.3 (europa). Mainly the eclipse standard installation - called classic - covers a lot of what has to be additionally installed in 3.2. A feature list of the classic install can be found here.
If you choose Eclipse Classic the installer automatically finds out, what system you are running at. Otherwise choose Other downloads for 3.3.
There is no need to explain anything here anymore, because the eclipse site is so beautifully designed, that you'll find any answer right the way.
Eclipse 3.2
With eclipse 3.2 a lot of new possibilities entered the way gaining a running standard eclipse installation within half an hour. In this article I focus on these major components:
- Eclipse Base SDK
- Callisto
- Subclipse
- SQL Editor
TODO (* Hibernate )
Therefore I don't fokus on the installation via your favorite distribution but through the native installation procedure into a local directory called simply eclipse or eclipse_VersionNumberwithin your home directory.
Why? If you like use your development environment on different plattforms (e.g. 64bit, 32bit, PPC), it is not possible to simply move your environment to an other computer. You have to install your eclipse installation from scratch on this particular machine - with all the plugins exactly the same concerning dependencies and versions.
If you don't do this, it is likely, that your developers - or yourself - will run into trouble when working with special sourcecode.
Prerequisites - Eclipse 3.2 SDK
Assuming that you installed java before, download the eclipse service development kit (SDK) for your platform from Eclipse Downloads. Put it into your home directory (or elsewhere) and unzip or untar it.
Now you should be able to start your base eclipse installation.
Use Callisto or Yoxos for most common Plugins
Until here everything is, like before. But there is a good solution for getting all the various plugins installed without any trouble, working together from the scratch by using a new tool
The latter can be used for allmost every commercial and non-commercial plugin for eclipse. For this service you'll have to pay an annual fee to Innoopract - the firm behind yoxos. This is a very useful and timesaving tool for getting done with the various dependencies between the different eclipse plugins.
There is a free version of yoxos, that contains a lot of free eclipse projects. Check it out.
Callisto however only summarizes - until now - 10 eclipse projects - enough for most of the projects around.
Sublipse Plugin
Maintaining your projects via subversion? Then you can use
for connecting eclipse to a subversion server.
It is always wise to store every project on the subversion server instead of managing different lokal installations of your projects!
My personally favorite method of gaining access to the svnserver is via ssh. The ssh connection only works with newer versions of subersion (greater 1.0.2). It uses the base authentification procedure of your system and needs no further configuration.
Open the svn perspective in eclipse and add a new location like this:
svn+ssh://username@servername_or_ip/directory/path/to/svn
Thereby you are addressing the svn directory on that server.
EPIC Perl Editor
For editing perl file with you can add the update site
http://e-p-i-c.sf.net/updates/testing
to you update manager an call it EPIC - Perl Editor
XSLT Editor
A good choice for an XSLT editor is the CPL licened one from Orangevolt.
The Update site:
http://eclipsexslt.sourceforge.net/update-site
Call it e.g. Xslt Editor - Orangevolt.
Detailed informations and documentation you'll find on http://eclipsexslt.sourceforge.net/.
JFace
JFace is now a well integrated part in eclipse 3.2. You can easyly add a preconfigured SWT library to your project. Don't forget to switch the JFace support on.
The only thing you have to do now is to add a new library called OSGI to your project. Search the
eclipse/plugins/org.eclipse.osgi_3.2.0.vJJJMMDD.jar
file and assign it to this variable. That's it.
All other manual activities necessary with eclipse <= 3.1 are not needed any more.
Velocity
The apache velocity project is a Java-based template engine:
"It permits anyone to use a simple yet powerful template language to reference objects defined in Java code. Velocity separates Java code from the web pages, making the web site more maintainable over its lifespan and providing a viable alternative to Java Server Pages (JSPs) or PHP."
The Veloedit is accessible as plugin for eclipse:
Poseidon
Make a directory called links to your eclipse directory
mkdir eclipse/links
Edit a file called
eclipse/links/com.gentleware.poseidon.ide_integration.eclipse.link.txt
with the following content path=/home/username/YourPoseidonInstallation/lib/poseidon
Restart eclipse. That's it.
ShellEd
An editor for unix shell scripts with sysntax highlighting. But the best is, that your shellscripts are fully integrated in your versioning system (cvs or svn).