At 06:14 PM 06/02/2000 -0700, you wrote:
>Ken Jenks wrote:
> >
> > vt replied:
> > >There was a full-fledged autoconf based system with all the features
> > >you've just listed, but it died a silent death due to the lack of demand
> > >;) If you lobby it up, I can reincarnate it ;)
> >
> > It sure would be helpful to just do the same kind of configuration as
> > Apache and PHP have, or even something easier.
> >
> > The may not be a big lobby for it on the mailing lists because people who
> > can't figure out how to install jBoss aren't likely to hang around and talk
> > about it. The biggest lobby is that "1000 Downloads a day!!!" boast --
> > minus the number of people on the mailing lists. Those thousands of people
> > who downloaded jBoss but aren't currently using it are a silent testimonial
> > to server configuration problems.
> >
> > Please reincarnate the full-fledged autoconf system for jBoss!
>
>Marc?
>
>I promise, it would *fully* cooperate with the current Ant build and
>just prepare the seamless build/install scripts that will wrap the Ant
>build into "./configure && make all install".
Since I wrote my plea for the autoconf system, jBoss has gone through a
major change and it's much easier to install and configure now. It would
still be nice to have the
./configure ; make all ; make test ; make install
that we Linux-heads are familiar with from Apache, PHP and friends, rather
than the jBoss-specific
sh build.sh
(Note that we can't just run ./build.sh directly because when you download
the build.sh file from CVS or unzip from the binary, build.sh doesn't have
execute permission set. This argues for binary distribution as a
traditional gzipped tarball, which most unzip programs can handle these days.)
-- Ken Jenks, http://abiblion.com/
Tools for reading.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
