ChangeLog

HEAD

• The POA now supports dumping classes without logging anything. This can be useful when dumping classes to then perform offline weaving with !AspectJ. To enable this mode, simply remove all transformations from the configuration file. The POA now also reports the number of newly dumped class files.

Version 2.0.1

This is a bug-fix release fixing some minor issues reported in the meantime. (see mailing list)

Version 2.0

• The Play-out Agent now also logs field set/get operations through reflection. The Booster can now convert these into regular field accesses. This aids static analyses that are field sensitive.
• The Play-out Agent now logs many more accessed to methods in the classes Array, Class, Constructor, Field, and Method. Further, new transformers can be added to instrument additional methods. This is done through a configuration file.
• The Play-out Agent and Play-in Agent now both use a configuration file and no longer support any command line options. When you first run one of the agent, a configuration file template will be written to $HOME/.tamiflex. Edit these files to your liking. If you want specific configurations for specific projects, you may place additional configurations files in those projects' directories: Tamiflex searches for the files first in the current directory and then in $HOME/.tamiflex. See here for more information: ConfigurationFile
• The configuration-file mechanism makes the Play-Out Agent extensible: users can now add their own instrumentation instructions.

Version 1.1.1

• Fixed a minor bug in the Play-out Agent, reported by Jochen Huck, related to path resolution on Windows systems.

Version 1.1

• Introducing the Booster, which makes TamiFlex compatible with static-analysis tools apart from Soot
• Numerous bug fixes, including a fix contributed by "Peng", which solves the problem of programs which call defineClass(..) with the class name being null

Version 1.0

Initial release