[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: request feedback on JBOSS debs





Joe Phillips wrote:> On Mon, 2003-01-20 at 05:00, Greg Wilkins wrote:

Your jboss debs for 3.0.2-2 deployed without problems on my
debian sid system.  Good work!

 + Does it really need to depend on your jdk1.4 package?
   Jboss can run on 1.3 and most debian users will have already
   installed jdk - having an extra 40MB download is a bit of a
   hurdle for most.


I don't think I explicitly depend on 1.4.  Nor do I depend on my j2sdk
package.  Across the different packages, I only depend on
java-virtual-machine, java2-runtime and java2-compiler.  I suppose that
if your system didn't have packages providing them, apt-get would want
to install my jdk.

OK - I have no packages that will provide that for me.  I have often
thought that dummy java2-runtime and java2-compiler packages should
be available for people who install externally.



 + The default webcontainer for jboss is Jetty, but you don't appear
   to allow just the default deployment - as it depends on tomcat.


I don't know what you mean by the default deployment.  jboss-tomcat is
it's own, optional package.  Note that jboss-server-all and
jboss-server-default depend on jboss-tomcat.  The deployment that my
packages install is straight out of the binary release from sourceforge.

<lightbulb>  Are you saying that the non-tomcat binary releases are
configured for jetty? </lightbulb>  If so, I was not aware of that.  I
figured they were jboss without any web containers.  I'll need to look
into this.

The lightbulb is 100watts and very bright!

Jboss default now includes jbossweb.sar which is really Jetty.  So an
out of the box JBoss contains a webtier.  Tomcat is an optional extra.

Maybe you need to create a jboss-web.deb with a description mentioning
that it includes the jetty servlet container.  Then jboss-tomcat can
be provided as an optional replacement for jboss-web.   You can't have
them both installed.

I figured this was a reasonable first revision.  We needed to get *some*
jboss packages on our systems.  I chose to make the packages pretty much
a stock binary distro from sourceforge just so I have *something* to
start with.  As you note, this is for simplicity.  I plan for future
revisions to start symlinking to jars within /usr/share/java.

Sounds a reasonable approach.

cheers



--
Greg Wilkins<gregw@mortbay.com>             Phone/fax: +44 7092063462
Mort Bay Consulting Australia and UK.          http://www.mortbay.com



Reply to: