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
