IBM, Teamstudio focus Java efforts

IBM and Teamstudio are focusing on Java tools this week, with IBM updating its AspectJ programming language extension and Teamstudio forming a separate division for its tools.

IBM has released Version 1.2 of AspectJ, an object-oriented extension to the Java programming language that is intended to enable “clean” modularization of functions such as error-checking and handling and synchronization, according to the company.

AspectJ supports aspect-oriented software development, enabling developers to write programs that are simpler, of higher quality, and easier to maintain than object-oriented counterparts, according to IBM. The paradigm is advantageous when a single problem statement or requirement does not easily map into a single class or module using object orientation alone.

Highlights of the 1.2 release of AspectJ include faster compilation and linking times. Incremental compilation, important when developing applications in an IDE, is significantly faster than in the previous release, IBM said. The language also has been extended to cover incremental linking of binary classes.

Also featured is an “adjoc” tool to create HTML pages for AspectJ programs, including cross references between program elements. Additionally, better out-of-box support is provided for linking aspects with applications at load time.

AspectJ 1.2 is available at no cost at https://eclipse.org/aspectjor at https://download.eclipse.org/technology/ajdt/aspectj-1.2.jar.

Teamstudio, meanwhile, has formed a separate division of the company, Enerjy Software, to sell the company’s Java tools line. The Teamstudio for Java product line will now be sold under the Enerjy Software moniker.

“Traditionally, we’ve been in the Lotus Notes development tool marketplace and I guess we were getting a lot of confusion once we set up TeamStudio for Java and were starting to sell tools for Java developers,” said Nigel Cheshire, CEO of Teamstudio and Enerjy Software.

Enerjy’s tools include Code Analyzer, for code auditing; Performance Profiler, to find performance bottlenecks in Java code; Memory Profiler, for detecting memory leaks; and Thread Profiler, to untangle threading problems.