eclipse 3.7 has been created in the repository HEAD branch, the version code-named Indigo (indigo).

The Mylar plugin for Eclipse (available for versions 3.1 and 3.2M3 only) is, without doubt, one of the most innovative ways to change out interaction with IDEs.

Let’s see a typical example of our daily work on Java project. You get a task, which can be an enhancement, new feature or bug fix. Typically, you have your project as a tree on the left-hand side, along with the list of all methods / fields (either as sub-branches of the project tree or as a separate tree). When you need to view or change source code, you either locate the corresponding entry in the project tree, or use one of the many shortcuts (such as Ctrl+Shift+T in Eclipse) to locate that class. Typically, you will need to access a number of classes, with a couple of methods in each one of them. Now, consider what happens in an existing project.

You have hundreds (if not thousands) of classes in tens of packages, each class having quite a few functions (depending on the previous team members, it can get to hundreds). The classes that you need to change for a particular bug fix are most likely under different packages. When you need to go back and forth between these classes, you waste valuable time (and energy) to do so. Wouldn’t it be nice to have a context view of your workspace. This view would contain only relevant branches of the project tree, the classes you are working on and the methods that you are changing. Ideally, the IDE itself would track the changes you are making to the codebase, continually updating the context view. Mylar plugin for Eclipse does exactly that.

Here are few screenshots that show the differences (before and after applying Mylar):

Outline of a single class – before Mylar (click to view full-size)

Outline of a single class – after Mylar (click to view full-size)

Outline of class tree – before Mylar (click to view full-size)

Outline of class tree – after Mylar (click to view full-size)

Few things should be noted. First of all, Mylar is very much work in progress, so there are quite a few quirks and exceptions. In addition, if your task spans more than 5-6 classes, and you work on more than one function in each class, the UI gets a little bit overstuffed (however, you can remove the context entries manually):

A FLAHS DEMO

http://www.eclipse.org/mylar/doc/demo/mylar-demo-04.html

This article shows you how to develop a Struts application in the Eclipse IDE, with the help of the Easy Struts plug-in. You’ll get an introduction to Easy Struts, installation and configuration steps, and instructions on building a basic Struts application through a progressive example. Different ways of enhancing the Struts application — such as connecting to a database, modularizing the application, internationalizing and localizing content, handling exceptions, and creating custom plug-ins — are also covered. Finally, you will learn how to deploy your Struts application on the Tomcat Web server.

Read more：http://www-128.ibm.com/developerworks/library/os-ecstruts/index.html

I recently started using Eclipse as my development environment, in part because of its support for the many platforms on which I develop, and in part because Eclipse is a great example of the power of an open, extensible environment in which people all around the world can contribute. I’m beginning to investigate the extensions people have come up with. For example, I use a little plugin called XMLBuddy to work with XML files, and it’s very helpful. So I became curious about whether anyone had written plugins to work with Hibernate, since I’ve done so much of that recently in putting together the Developer’s Notebook. It turns out there are several such efforts underway; in this article we will explore one of them — the Hibernate Synchronizer.

http://www.onjava.com/pub/a/onjava/2004/06/23/hibernate.html?page=1