Kathey Marsden wrote: > I think you are right that new functionality might indeed need to > require new permissions, but existing tests and functionality should run > with the currently documented permissions. I am not sure what > functionality your classloader work adds, but tests for the new product > functionality might reasonably require new permissions. Existing tests > should just work with the currently documented permissions.
To catch regressions as you describe we would need to modify the test harness to allow tests to have specific permissions granted to them. Then the single test policy we have now would be required permissions for Derby (e.g. property reads, class loader for embedded) and then the _app.properties file for a test would add in selected permissions. That would be a great improvement, a step up from the current testing, where the set of permissions granted to a Derby jar is the union of all permissions required for all tests. Dan.
