Tasks

Lists of todos and ideas for future version (see also Wish List ).

0.6

  • switch to Java 6 and AspectJ 1.6
  • reactivate ant test the Ant and Maven plugin

0.5

  • create a new CVS modul "PatternTesting05"
  • switch from Maven 1 to Maven 2 and set up a new directory structure
  • import bit for bit of the existing sources (but not the Maven1 plugin)
  • switch to Java 5 and AspectJ 5
  • scan the todos for 0.4 to see what can be realized

0.4

  • Improve Documentation.
  • Merge runtime report with compile time report
  • Add support to Logger for logging warnings and errors versus the generic PTViolation.
  • Refactor Maven plugin to depend on AspectJ plugin where possible
  • Add ability to enable/disable PT plugin
  • Add ability to fail the build based on PT error.
  • Add support for runtime aspects by providing a base class that adds violations to an XML file, which gets transformed into HTML after the tests are run. Modify the maven plugin so that it supports weaving pattern test aspects into the main classes so that these tests are triggered when running the unit tests ( Maven "test" goal). Will need to extend that to Cactus tests and functional tests later on.
  • Add notion of listeners to AjcErrorHandler. Provide 2 listeners: XMLFormatter and PlainFormatter (stdout). Same as for the junit Ant task.
  • Improve AjcTestCase by providing assertXXX() APIs to more easily assert result from Ajc.
  • Move the "declare error" from AbstractXXXTestPattern to the concrete implementations in the Maven plugin and add ability for users to define the text to be printed. Indeed, in order to get informative error message, it needs to be provided by the application, in its context.
  • Create a generic test case as all junit test cases seem to follow the same pattern.

Unassigned

  • Fix issue with Avalon ThreadSafe pattern test: it should not be triggered by static variable initializations.
  • Add support for JBossAOP.
  • Add support for AspectWerkz.