On Thu, 15 Nov 2001, David Jencks wrote: > Then you are insisting on wasting your time and the time of everyone on > this list. You will only get the correct cvs versions of the entire jboss > server by checking out jboss-all. The server (looks like jboss in cvs) is > only a small part of jboss and will not build or be of any use to anyone, > even debian fanatics, by itself.
I never said I would only check out just jboss. I said I would package each module individually. Why can I not build the modules separately? What is the hardship? For instance, I see a separate JBossMQ release. Why is this released separately, if jboss is supposed to be built as one? > Checking out jboss-all is different from using the build system. I can't > imagine why you want to duplicate the work done to put together the current > build system, and doubt anyone will want to maintain it separately if you > do. Why is the build system for jboss separate from jboss? > The relationship between the build.xml file in build and those in the other > modules is similar to the system of makefiles in which each directory has > its own makefile and calls those in subdirectories. Do you rewrite make > systems to avoid this kind of unified, easy to use packaging? No, of course not. But the build system in jboss-all that wraps everything else is not the same as being able to build each module separately. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
