• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • hhuynh
  • Reporter: juris
  • August 16, 2007
  • 0
  • Watchers: 0
  • October 29, 2007
  • October 11, 2007


There are some instrumentation config that will always be (or currently be) required, as well as some terracotta configuration that doesn’t have a home yet or does not warrant (yet) a config-bundle all its own. This module could house/create these configurations. This module will always be installed and started.

Here are some of the configuration that it should create (very likely more):

  • exclusion of obfuscated classes (com.sun.crypto.provider..*, etc)
  • specify permanent excludes
  • include javax.swing model classes (eg: javax.swing.AbstractListModel)
  • include java.awt model classes
  • etc.

We could add a terracotta.xml file in modules-common config bundle instead of creating a new one for this purpose.


Juris Galang 2007-08-16

we should always exclude com.sun.crypto.provider classes

Fiona OShea 2007-08-17

I think this is related to CDV-326

Juris Galang 2007-10-11

This is completed. There more configs that we can pull out of stdcfghelper, but we should step back and formulate a way to organize and group these configurations (beyond the obvious 3rd party TC configs)

Fiona OShea 2007-10-29

Hung as you have been involved in testing the Forge in the early stages can you verify that these issues are resolved? thanks