I will start working on this today. I assume this is more important than the NNTP stuff I need to finish up?
--jason On Thu, 15 Nov 2001, marc fleury wrote: > Adam, > > while the tone is really not appropriate (only I get to bang on Jason like > that), I agree that BM can be frustrating. It is however functional and > powerful, we do need a simple file describing "this is how to build". Right > now the BM paper is way too complex, I am not sure we need to understand how > bm works, just how to build the files. > > That "readme" is missing and it can frustrate newbie developers like you but > really Jason we do need a "README-BUILD" file at the top of the directory > something that says. "Go to build/, type sh build.sh or build.bat according > to platform, the results will be in output/, have a good day" and basta! > > the build.sh in server can confuse newbies, (ehmmm and me as well :) > > marcf > > > |-----Original Message----- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Adam > |Heath > |Sent: Thursday, November 15, 2001 2:19 AM > |To: Jason Dillon > |Cc: JBoss Development > |Subject: RE: [JBoss-dev] can't build jboss from cvs > | > | > |On Wed, 14 Nov 2001, Jason Dillon wrote: > | > |> If you are trying to build a 3.0 .deb then please use the > |'jboss-all' module > |> from cvs and use 'build/build.sh release' to create a release > |suitable for > |> stuffing into the package. The files will be inder > |'build/output/jboss-*/ > | > |Ok, I've done this, and everything has built fine. > | > |The layout of build/output looks useable, and I can produce debs from that. > |I'll be moving stuff around, to make it fit properly in FHS. I'll > |be making > |some things into symlinks, to give jboss a correct view on the world. In > |other cases, I'll modify the configuration files to access the correct > |locations directly. > | > |Now, to the biggest issue with all this. Could the final jboss > |tarball that > |is created, *NOT* have any external source? I can understand > |having a tarball > |that does have this source, but could it be called > |jboss-bundle-src.tar.gz, or > |something. If there is no source tarball that is in this pristince state, > |then I will not be able to upload jboss to Debian, because then it > |would mean > |that Debian is distributing non-free software, which is not allowed. > | > |Making debs of course, doesn't really matter about what is > |included and what > |isn't. But for actual upload to the Debian archive(and all its mirrors), I > |*NEED* this non-free code and external code removed from the > |source tarball. > |Even if this means the build system contains broken references to these > |missing files, that is fine. > | > |Additionally, I tried setting build.compiler=jikes in > |build/build.xml, but it > |didn't compile blindly fast. Is this the correct way to use jikes? > | > | > |_______________________________________________ > |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
