You shouldn't have any .jars or classes specified in a classpath. You also should not have an ANT_HOME specified. The build.sh is designed to look and find the ant installation in ./jboss-all/tools/bin. It and all the build.xml(s) specify their classpath(s). I take it that you have checked out the entire jboss-all CVS archive and are building everything? And it is all building except for jboss.net? If so, what errors are you getting? If not, try to check out it all out and execute the build.sh in ./jboss-all/build . It should build "most" everything including jboss.net. Worst come to worst, afterwards just copy the jboss-net.sar out of the ./jboss-all/jboss.net/output/lib and into your existing ./jboss/server/default/deploy directory. Does that help?
Frederick N. Brier At 11:25 PM 6/10/2002, you wrote: >I read the instructions on the developers web site (dotnet.jsp), but my >attempts to build the jboss.net modules have resulted in various failures. >I was able to figure out that ant needs to be executable and the "build" >needs to be "build.sh", but it looks like that at the very least my >classpath is missing some important jars. Do those instructions work for >everyone else? If not, are there any other instructions that work better? > >_______________________________________________________________ > >Don't miss the 2002 Sprint PCS Application Developer's Conference >August 25-28 in Las Vegas - >http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
