MaintainJ Plugin Changelog
What's new in MaintainJ Plugin 4.0.0
May 12, 2012- This release adds the response time tuning capability in a single user environment:
- Response Time View - The sequence diagram and the corresponding 'Outline view' are redesigned to allow the user to quickly find the methods that are taking the maximum response time in a use case.
- Filter Calls by Response Time - This feature allows the user to filter out all the calls whose response time is less than the specified time.
- Delete All Classes Except - This feature can be used to quickly see the interactions between the important classes in the use case.
- Shows the number of times a method is called in a loop - MaintainJ always removed the loop and recursive calls to avoid cluttered sequence diagrams. This version adds the feature to show the number of times a method is called in a loop.
- Opening trace files generated using older versions - To open the trace files generated using the older versions of MaintainJ, copy them to the 'MaintainJ Trace Files Project' created using this release. This project can be created by following File->New->Project->MaintainJ->MaintainJ Trace Files Project. Please note that the trace files from older verisons do not have information about the number of times a method is called in a loop.
New in MaintainJ Plugin 3.6.1 (Mar 17, 2012)
- Export the diagrams to UML2 - The package name of the return type of a call was not shown in the last release. This release fixes the issue. If the method parameters (or the return type) are of an array type, they were not shown properly in the last release. This issue is fixed as well.
- When call context is captured, the previous release did not generate a merged trace file of all the threads. This release generates the merged trace file for all threads.
- MaintainJ removes the loop and recursive calls by default. A system property is introduced to turn this off if necessary.