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
On Mon, 3 Sep 2001, Scott M Stark wrote:
> Is the testsuite supposed to be building yet? I see numerous errors and
> warnings. The warnings are due to the junit3.7 deprecation of the assert()
> method in favor of assertTrue()
>
> testsuite 1064>./build.sh
> Searching for build.xml ...
> Buildfile: /home/starksm/cvsroot/Main/jboss-all/testsuite/build.xml
>
> init-buildlog:
>
> init:
> [moduleinfo] Project root: /home/starksm/cvsroot/Main/jboss-all
> [moduleinfo] Module root: /home/starksm/cvsroot/Main/jboss-all/testsuite
>
> compile-classes:
> [mkdir] Created dir:
> /home/starksm/cvsroot/Main/jboss-all/testsuite/output/classes
> [javac] Compiling 274 source files to
> /home/starksm/cvsroot/Main/jboss-all/testsuite/output/classes
> [javac]
> /home/starksm/cvsroot/Main/jboss-all/testsuite/src/main/org/jboss/test/bank/
> ejb/AccountBean.java:8: cannot resolve symbol
> [javac] symbol : class CreateException
> [javac] location: package ejb
> [javac] import javax.ejb.CreateException;
> [javac] ^
> [javac]
> /home/starksm/cvsroot/Main/jboss-all/testsuite/src/main/org/jboss/test/util/
> ejb/EntitySupport.java:8: package javax.ejb does not exist
> [javac] import javax.ejb.*;
> [javac] ^
> [javac]
> /home/starksm/cvsroot/Main/jboss-all/testsuite/src/main/org/jboss/test/util/
> ejb/EntitySupport.java:18: cannot resolve symbol
> [javac] symbol : class EntityBean
> [javac] location: class org.jboss.test.util.ejb.EntitySupport
> [javac] implements EntityBean
> [javac] ^
> ...
> [javac]
> /home/starksm/cvsroot/Main/jboss-all/testsuite/src/main/org/jboss/test/testb
> ean/test/Main.java:632: warning: assert(java.lang.String,boolean) in
> junit.framework.Assert has been deprecated
> [javac] assert("pkBean != null", pkBean != null);
> [javac] ^
> [javac] 100 errors
> [javac] 125 warnings
>
> ----- Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, September 03, 2001 10:21 PM
> Subject: [JBoss-dev] build system change
>
>
> > I finished the first round of modifications to the jboss-* modules, to
> make
> > it easier to share modules between projects. The release mechanism has
> been
> > moved to the control module, which will pull the generated files from the
> > source module after that module has been executed.
> >
> > I did away with the 'min' targets. They were mostly useless. I am
> keeping
> > the most targets though, and using them as the default in most cases.
> >
> > I have not had time to update jboss-docs, jboss-website or jboss-mq with
> the
> > new release semantics, but I should get to that soon.
> >
> > I left the release-* targets in each source module, but all that is really
> > used for now is creating an archive of the files under output/*.
> Eventually
> > this mechanism could be used for plugins to generate a .sar (.jsr, .ear,
> > whatever), so some docs them make a nice archive of it.
> >
> > The release-dependencies have all moved to the control module, which means
> > that I had to move over the thirdparty properties too. I don't really
> like
> > that too much, but in the short term there is no way to get around it.
> >
> > I also tried to remember to give each build.xml a valid name, for those
> who
> > have ide's which use that value. I also tried to change the
> > junit.jvm.options to -Ddummy from -client.
> >
> > It looks like Ant 1.4 will allow <path> elements to be created from inside
> > of a <target>, so once I have finished updating the projects, I might look
> > to moving everything that is currently outside of a <target> into one.
> This
> > will make it easier to group properties and patsh with helper tasks
> > together. Like for the path convertion task, which might be required for
> > the manual module under win32.
> >
> > Let me know if there are any problems.
> >
> > --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
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
