Re: [jboss-as7-dev] Security manager test runs
Perhaps the pull request job should be set up to use the security manager, and the
master-ignore job to not use a security manager (or the other way round). That way pretty
much everything should be tested both ways before merged upstream.
Then the question is what to do with the master job which runs every time something is
merged into master. Perhaps we need another job, running once a day, which runs with the
opposite security manager config from the master job?
On 28 Feb 2013, at 15:52, David M. Lloyd wrote:
The AS codebase now supports running under a security manager. Well,
sort of. There are a few places where we need privileged blocks and/or
permission checks, but you can boot up AS under a security manager today
if you want. Just follow these steps:
1. Modify standalone.sh so that the -secmgr flag is passed in to JBoss
Modules.
Well, I guess there's just the one step. Anyway I've noticed that the
impact on startup time is not as bad as I had expected, which is good.
So the question is: Should we set up a security manager-enabled test
run? How should it work?
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
---------------------------------------
Kabir Khan
Prinicipal Software Engineer
JBoss by Red Hat