1 Reply Latest reply on Oct 19, 2005 4:46 PM by Scott Stark

    SecurityManager tests

    Adrian Brock Master

      I've added some simple support to run tests with a SecurityManager enabled.
      The implementation is currently a "hack" in that it is enabled it just detects what should
      have all or no permissions based on the ending of the codebase.
      i.e. it requires the classes to be in either:

      output/classes - all permissions
      output/classes-tests - no permissions
      rest-of-classpath - all permissions

      See test/src/main/org/jboss/test/security/TestsPolicyPlugin.java

      Anybody have a better idea? It would obviously be better to have a more
      intuitive, finer grained and more declarative approach.