The source for 2.4.x, no matter how you get it, uses a build system
incompatible with the source for 3.0, which you get by checking out
jboss-all. I think to check the source for 2.4.x out of cvs you have to
check out each module under their cvs directory name (jboss, jbosscx, etc)
independently and build each independently. The dependencies between the
resulting jars are rather tricky to get right, thus the new build system.
As I recall you don't need CLASSPATH set to build the modules, although I
haven't built 2.4.x for a long time.
Try again with only one version at a time.
david jencks
On 2001.09.17 14:36:19 -0400 Dean Anderson wrote:
> I'm using RH 7.1 (intel) Linux, JDK1.3.1 from sun.
>
> [dean@commander dean]$ echo $JAVA_HOME
> /usr/local/jdk1.3.1
> [dean@commander dean]$ echo $CLASSPATH
> /usr/local/jdk1.3.1/lib/tools.jar:/usr/local/jdk1.3.1/lib/oracle.jar:/usr/lo
> cal/jdk1.3.
> 1/lib/interclient.jar:/usr/local/jdk1.3.1/lib/htmlconverter.jar:/usr/local/j
> dk1.3.1/lib
> /dt.jar:/usr/local/jdk1.3.1/jre/lib/ext/servlet.jar:/usr/local/jdk1.3.1/jre/
> lib/ext/par
> ser.jar:/usr/local/jdk1.3.1/jre/lib/ext/jsse.jar:/usr/local/jdk1.3.1/jre/lib
> /ext/jnet.j
> ar:/usr/local/jdk1.3.1/jre/lib/ext/jcert.jar:/usr/local/jdk1.3.1/jre/lib/ext
> /jaxp.jar:
> [dean@commander dean]$
>
> I downloaded from 2.4.1 and 2.4.0 (plain, not Jetty or Tomcat) from
> Sourceforge. (src dir, no build environment, nothing like jboss-all)
>
> used cvs from :pserver:[EMAIL PROTECTED]:/cvsroot/jboss to
> get
> jboss-all
>
> cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/jboss co jboss-all
> cd jboss-all
> cvs update -d
> cd build
> sh build.sh
>
>
> _______________________________________________
> 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
