This content has been marked as final.
Show 5 replies
-
1. Re: Alternative parameters in startup script
ryan.campbell Apr 24, 2006 10:23 AM (in response to kabirkhan)http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsRequiringCustomConfiguration
Parameters can be passed to JBoss using the server:config task, look at the ServerController Tasks referenced from the above wiki page. -
2. Re: Alternative parameters in startup script
kabirkhan Apr 25, 2006 6:39 AM (in response to kabirkhan)Is the 4.0 testsuite run using both jdk 1.4 and jdk 5.0? If so, I would need two different server:configs for the different dists of jboss for running this test (jboss-4.0x for JDK 1.4 and jboss-4.0.x-ejb3 for JDK 5.0), and the wiki page says that only one is allowed per build.xml?
Ideally, it would be possible to do something like:<!-- JDK 5 --> <server:start name="all" jbossHome="${jboss.dist.50}"> </server> <!-- JDK 1.4 --> <server:start name="all" jbossHome="${jboss.dist.14}"> </server>
For jboss-head I can use the same jboss dist, so I don't think there is a problem there. -
3. Re: Alternative parameters in startup script
starksm64 Apr 25, 2006 9:06 AM (in response to kabirkhan)The testsuit is run with both jdk 1.4, 1.5, but we don't change the codebase run. Its always the jboss-4.0.x dist. We would have to add another jboss-4.0.x-ejb3/jdk5 specific set of tests.
<target name="jboss-4.0.x-ejb3-tests"> <server:start name="all" jbossHome="${jboss.dist.50}" /> ... </target>
-
4. Re: Alternative parameters in startup script
kabirkhan Apr 25, 2006 10:31 AM (in response to kabirkhan)
The testsuit is run with both jdk 1.4, 1.5, but we don't change the codebase run. Its always the jboss-4.0.x dist.
ok, I think that's fine for my purposes, the test in question doesn't use any jdk 1.5 features. I will try it out.
I assume that the ejb3 tests have their own thing starting the server from the correct codebase. -
5. Re: Alternative parameters in startup script
starksm64 Apr 25, 2006 10:43 AM (in response to kabirkhan)"kabir.khan@jboss.com" wrote:
I assume that the ejb3 tests have their own thing starting the server from the correct codebase.
Yes.