All aboard the Eclipse bandwagon

After BEA, Borland, Nokia, Oracle, Sybase… it’s now Compuware who has jumped on to the Eclipse bandwagon.

Compuware has announced that the company has made a strategic, long-term commitment to the Eclipse Foundation by becoming an Eclipse Strategic Developer.

As part of this commitment, Compuware will focus its efforts on application life cycle integration and tool interoperability and dedicate resources to the Eclipse Application Lifecycle Framework (ALF) project. Compuware’s move sends a strong signal of support to the initiative aimed at making life cycle integration a key part of Eclipse’s future. By creating an industry standard for tool interoperability, Compuware seeks to help customers cost-effectively improve the delivery of applications across the life cycle.

Compuware will contribute resources — including developers and a future code contribution of Compuware integration technology — to Eclipse and has pledged to lead an Eclipse project in the near future. These contributions are in addition to Compuware development resources already integrating Eclipse technologies into Compuware products, as well as additional product integrations planned for the future.

Source: Compuware Press Release

Ed: If you are wondering what’s happened to the NetBeans platform and is it as good as dead? We will have answers to all your NetBeans questions very soon…Stay Tuned!

>> Eclipse vs NetBeans
>> NetBeans moving fast, could soon threaten Eclipse’s leader position
>> Java IDE comparison: Borland JBuilder tops
>> Expect JDeveloper to grow at an Unexpected pace
>> JDeveloper is the most comprehensive Java IDE available

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!

0 thoughts on “All aboard the Eclipse bandwagon

  • November 20, 2008 at 7:49 pm

    While JTiger addresses some of the deficiencies of JUnit, it’s not perfect either. It doesn’t address that code separation between the test framework and the test application. Why do I need to spoof my test code with JTiger’s annotations?
    I agree JUnit isn’t the best. However, I don’t want to move to JTiger only to find there is another refinement and I have to change my unit tests again. I believe JTiger isn’t there yet.

Leave a Reply