For many Java developers,
Eclipse is an IDE. Since Eclipse RCP became popular with the release of Eclipse 3.1 last June, many see it as an IDE for RCP.
But the real strengths of Eclipse stem from its design as a tool integration platform. This has both technical and business implications. Consider the Eclipse
Apogée project.
- The project's technical architecture requires complex integration of many different technologies. Because Eclipse tooling allows rapid development of tools which can work well together because of the eclipse plug-in architecture, it is possible for the project architects to leverage an amazing range of technology. Check out the project proposal.
- The flexible open source license used by Eclipse also allows a wide range of proprietary and open source projects/organizations to plug into the effort. The most recent example is the decision of db40 to join the project to help with persistence.
On a more modest level, products like
myeclipseide and Eclipse projects like
WTP illustrate use of Eclipse as a server-side tool box. One can simply spend 15 minutes browsing the rich variety of Eclipse projects to see many more examples of the technical and business ecosystem that is emerging.
An examination of the technical archiecture of Apogée is worth while. Products like db40 and Mylar are far beyond the experience or knowledge of most good developers. They provide knowledgeable developers much a much deeper toolset than most opensource projects utilize. For simple projects this can be overkill, but it makes it possible to address a wider range of problems.