User: starksm
Date: 02/02/25 11:49:52
Modified:src/main/org/jboss/test JBossTestServices.java
Log:
Do not print out the beancount, iterationcount and threadcount values
in their accessors as if these are as loop bounds the values are
printed N times.
Revision Changes
User: user57
Date: 02/01/02 20:01:01
Modified:src/main/org/jboss/test JBossTestServices.java
Log:
o migrated all components to a new JMX domain name model. jboss.system
is now where to core/spine components live. moved all components that
were in JBOSS-SYSTEM that
User: starksm
Date: 01/09/18 01:23:25
Modified:src/main/org/jboss/test JBossTestServices.java
Log:
Use single deploy/undeploy of the security-spec.jar
Revision ChangesPath
1.2 +8 -5 jbosstest/src/main/org/jboss/test/JBossTestServices.java
Index:
Is there some reason you changed all the methods to public here instead of
using the JBossTestSetup for the setups in all the security tests?
david jencks
On 2001.09.18 04:23:25 -0400 Scott M Stark wrote:
User: starksm
Date: 01/09/18 01:23:25
Modified:src/main/org/jboss/test
Yes, I did not see JBossTestSetup as none of the TestSetup code
had been converted to use it.
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 5:22 AM
Subject: Re: [JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test
User: d_jencks
Date: 01/09/17 10:33:53
Modified:src/main/org/jboss/test JBossTestCase.java
Added: src/main/org/jboss/test JBossTestServices.java
JBossTestSetup.java
Log:
Finished converting to JBossTestCase for deploy and logging. Security tests