'testsuite' does not build anything, it simply runs the jboss/testsuite
'tests' target. Too build everything, then run the testsuite, use most,
main or all as the target to execute before testsuite.
./build.sh most testsuite
'all' will simply make docs too, which aren't very useful for testing.
The 'run-nightly' target should update, clean, build, start jboss, run the
tests, stop jboss then generate reports. If you are trying to setup a
recurring testsuite run then it should be used. It might need to be update
for these latest changes though.
Invoking all child modules, even if they don't build anything, isn't a fast
process. I think there are still some problems past that though. I had to
create a new jndi.properties in src/resources because I couldn't really
figure out where the jndi.properties came from before. Could be that there
were some other files included in this mysterious way which I have missed.
--jason
the most On Tue, 4 Sep 2001, Scott M Stark wrote:
> The testsuite is expecting that a number of packages have been built but it
> is not validating that they have. This is the source of the numerous errors.
>
> ----- Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: "Scott M Stark" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, September 03, 2001 11:35 PM
> Subject: Re: [JBoss-dev] build system change
>
>
> > Yup, it does work... mostly. Did you get any of the email that I sent to
> > you about the security tests?
> >
> > I think there might be some config or file placement issues. I had to
> > change the way several jar files were being created to avoid having one
> jar
> > build be dependent on the jar build before it (ie. movies files around to
> > get a jboss.xml and ejb-jar.xml file). I would really like to change all
> of
> > these to use the <war> <ear> and <ejbjar> tasks, but that will required
> more
> > time than I have at the moment (my guess is that it could be done in 2
> > days).
> >
> > We should really replace assert() usage. It is on my list of things to
> look
> > into further, along with a common JBossTestsuite class, and other
> testsuite
> > improvements.
> >
> > I would rather not turn of deprecation warnings if it can be avoided.
> >
> > --jason
> >
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
