Tools
Release History
jMetra 1.2.5 Release - What's New?
This release is externally not that different. Its main purpose was to increase performance and fix several parsing issues that occurred within code produced within Eclipse.
Bug Fixes
The most noted bug was that non-printable characters at the end of a source file would result in the parser errors and therefore jMetra would not collecting metrics for those files. This has been corrected.
jMetra 1.2.4 Release - What's New?
Metrics can now be collected for the JDK 1.5 grammar. During the collection stage, use -javaversion 1.5 to parse 1.5 java source code.
Bug Fixes
Several bugs have been resolved relating to confusion by jMetra when certain combinations on command line options where used simultaneously.
jMetra 1.2.3 Release
Metrics charts in the jMetraDoc now have the flexibility to display by time or by data sampling along the X axis. This provides more flexibility for how you display the data you collect. For projects with more sporadic measurements over long periods, this may be a more desirable option for viewing.
jMetra 1.2.2 Release
What's new?
Generation of jMetraDoc's Project page can now show the change in metrics between the recent metrics collected and an arbitrary past collection of metrics specified by the label.
jMetra 1.2 Release
What's new?
Generated jMetra Doc now utilizes cascading style-sheets (css). A default css is provided, but a custom css may be specified.
The jMetra Doc generation process is now based on template files for the html Doc. Users may modify the templates to customize the look-and-feel or layout of their pages. Users may even customize the generated pages to link to pages generated by other analysis/metrics tools. The jMetra Doc templates leaverages the FreeMarker template engine.
jMetra Doc identifies what packages or classes are not currently part of the project.
The aggregation processing time is now reduced since an index file identifies what builds have already been aggregated.
Integration with Ant logging is added when the executing context is within Ant. If run via command line, the default log4j logging is used.
Summary metrics are now provided at the project level jMetraDoc page.
Backward Compatability
jMetra 1.2 can be used to aggregate and generate jMetra 1.2 jMetraDoc using metrics files generated from all past versions of jMetra. Try it, and gain all the extra advantages of the new version!
Bug Fixes
Packages containing no java classes are no longer included in the resulting metrics files.
Prev / Next Package navigation only allowed navigation between packages at the same level. Package navigation now traverses the flattened package list as it appears in the project page. Known Bugs
The jMetraDoc option for selectively producing doc for particular packages will always include the parent packages, regardless of whether the -incparents option is included.
Using the -label option to assign an arbitrary name to the build (and the corresponding metrics file) can cause problems during the jMetraDoc stage. This jMetra bug will be fixed by 6/31/03. If you still wish to use the -label option to name your build, you may work around the bug by making sure that each new metrics file is always aggregated immediately after it is generated. Alternatively, the problem is avoided if your labels are always in increasing sorting order. For example, build0001, build0002,....... build0010, build0011, etc.
Due to rounding errors, the percentages on the jMetraDoc project page may not add up exactly to 100%.
jMetra 1.1.3 release
what's new / what's fixed
Crimson has been replaced with Xerces 2.2.1.
Problems are fixed relating to erroneous parsing of java files containing comments after the closing bracket of the class (at the end of the file). This is most commonly encountered by IntelliJ and TogetherJ users that opt to include autogenerated comments in their java files.
The output directory for the aggregation would always use the default relative directory /aggrbuild, ignoring the command line argument. This has been corrected. The aggregration output will now use the specified command line argument
JDK 1.4 keywords are supported
Directories under source roots containing no java files or subdirectories with java files were included in metrics collection and reports. They are now ommitted from metrics collection. Note that existing users that have empty or null packages in pre-existing build xml files generated prior to 1.1.3 must manually remove them from the xml files and re-aggregate the builds.
jMetra 1.1.2 release
Bug Fixes
jMetra was not friendly for Unix - it had problems using the correct seperator based on environment.
Fix: jMetra now runs successfully on Unix. All pathes are constructed using the seperator appropriate to the environment.
Problems with command line arguments using relative paths.
Fix: jMetra how supports both absolute and relative path and file command line arguments.
Parsing problems would result in ambigous stacktraces, and jMetra would sometimes choke.
Fix: jMetra will always recover from a failed attempt to parse a java file by logging the information to standard out and an error log, and continue.
When parsing problems would occur, the particular file causing the problem was not identified.
Fix: jMetra will include the file causing the problem in both standard out and an errors log file.
