> On Wed, 14 Nov 2001, Jason Dillon wrote: > > > What are you talking about? build.sh makes no assumptions about the users > > classpath and sets it up correctly to use the jars from tools/lib. > > There are no jars whatsoever in jboss cvs. Please, don't just assume > something.
Ok, now I am really confused. There are .jar files in the 2.4 and MAIN cvs modules for jboss, jboss-all/thirdparty and jboss-all/tools. They are required to build the sources and produce a runnable JBoss distribution. > build.sh does NOT handle the planet57 stuff. Please read what I said, again, > 3 times, then read it again. Of course it does. That is what it does; it sets up the environment so that the build will have the correct classpath and environment variables to run correctly. > Running build.sh WILL fail. Period. No attempt is made by it to handle ALL > external dependencies that jboss has. And I don't think there should be an > attempt. There are already systems that exist that handle that(debian has > one). There exist people(debian maintainers) that excel in this kind of > distribution packaging. What? Last I checked build.sh works fine. How are you building? Where did you get your sources from? What platform/os version are you using? What version of the JDK are you using? Please explain, this is very disconcerting. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
